Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix spark connector 3.2.0 documentation #353

Merged
merged 2 commits into from
Nov 28, 2023
Merged

fix spark connector 3.2.0 documentation #353

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21d4b74
fix spark connector 3.2.0 documentation
nlu90 Nov 28, 2023
5b42a51
more fix
nlu90 Nov 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions data-processing/pulsar-spark/3.2.0/pulsar-spark.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,10 +49,11 @@ The whole life cycle of a structured streaming job is illustrated in the figure

You can set the following configurations for the Pulsar Spark connector.

{% raw-html %}
<table class="table">
<tr><th>Option</th><th>Value</th><th>Required</th><th>Default</th><th>QueryType</th><th>Description</th></tr>
<tr>
<td><code>service.url</code></code></td>
<td><code>service.url</code></td>
<td>The Pulsar <code>serviceUrl</code> configuration.</td>
<td>Yes</td>
<td>None</td>
Expand Down Expand Up @@ -116,7 +117,7 @@ You can set the following configurations for the Pulsar Spark connector.
<td>The timeout for reading messages from Pulsar, such as <code>6000</code>.</td>
</tr>
<tr>
<td><code>waitingForNonExistedTopic`</td>
<td><code>waitingForNonExistedTopic</code></td>
<td>
* <code>true</code><br>
* <code>false</code>
Expand Down Expand Up @@ -152,7 +153,7 @@ You can set the following configurations for the Pulsar Spark connector.
<td> The <code>endingOffsets</code> option specifies where a Reader stops reading data.<br />* "latest": the Reader stops reading data at the latest record.<br />* A JSON string: specifies an ending offset for each topic.<br><br><b>Note</b>:<br><br><code>MessageId.earliest ([8,-1,-1,-1,-1,-1,-1,-1,-1,-1,1,16,-1,-1,-1,-1,-1,-1,-1,-1,-1,1])</code> is not allowed.</td>
</tr>
<tr>
<td><code>failOnDataLoss`</td>
<td><code>failOnDataLoss</code></td>
<td>
* <code>true</code><br>
* <code>false</code>
Expand All @@ -163,7 +164,7 @@ You can set the following configurations for the Pulsar Spark connector.
<td>Specify whether to fail a query when data is lost (For example, topics or messages are deleted because of the retention policy). This may cause a false alarm. You can set it to <code>false</code> when it does not work as you expected. A batch query always fails if it fails to read any data from the provided offsets due to data loss.</td>
</tr>
<tr>
<td><code>allowDifferentTopicSchemas`</td>
<td><code>allowDifferentTopicSchemas</code></td>
<td> Boolean value </td>
<td>No</td>
<td><code>false</code></td>
Expand Down Expand Up @@ -195,6 +196,7 @@ You can set the following configurations for the Pulsar Spark connector.
<td> Data in Pulsar topics is actually written out using the Pulsar Producer API. Therefore, you can configure Producer-related settings by specifying the <code>pulsar.producer.*</code> option. For details, see <a href="https://pulsar.apache.org/docs/client-libraries-java/#configure-producer">Pulsar Producer Configuration</a>.</td>
</tr>
</table>
{% /raw-html %}

### Schema of Pulsar Spark source

Expand Down