Github user tcondie commented on a diff in the pull request:
https://github.com/apache/spark/pull/16918#discussion_r101168119
--- Diff: docs/structured-streaming-kafka-integration.md ---
@@ -187,50 +306,68 @@ The following options must be set for the Kafka
source.
The following configurations are optional:
<table class="table">
-<tr><th>Option</th><th>value</th><th>default</th><th>meaning</th></tr>
+<tr><th>Option</th><th>value</th><th>default</th><th>query
type</th><th>meaning</th></tr>
<tr>
<td>startingOffsets</td>
- <td>earliest, latest, or json string
- {"topicA":{"0":23,"1":-1},"topicB":{"0":-2}}
+ <td>"earliest", "latest" (streaming only), or json string
+ """ {"topicA":{"0":23,"1":-1},"topicB":{"0":-2}} """
</td>
- <td>latest</td>
+ <td>"latest" for streaming, "earliest" for batch</td>
+ <td>streaming and batch</td>
<td>The start point when a query is started, either "earliest" which is
from the earliest offsets,
"latest" which is just from the latest offsets, or a json string
specifying a starting offset for
each TopicPartition. In the json, -2 as an offset can be used to refer
to earliest, -1 to latest.
- Note: This only applies when a new Streaming query is started, and that
resuming will always pick
- up from where the query left off. Newly discovered partitions during a
query will start at
+ Note: For Batch queries, latest (either implicitly or by using -1 in
json) is not allowed.
--- End diff --
Agreed. The previous version had "S" caps, so I wasn't sure if this was a
convention or not. I'll make the correction.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
