You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/structured-streaming-kafka-integration.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -368,7 +368,7 @@ The following configurations are optional:
368
368
<td>none (next preference is <code>startingOffsetsByTimestamp</code>)</td>
369
369
<td>streaming and batch</td>
370
370
<td>The start point of timestamp when a query is started, a string specifying a starting timestamp for
371
-
all partitions in topics being subscribed. Please refer the details on timestamp offset options below. If the matched offset doesn't exist,
371
+
all partitions in topics being subscribed. Please refer the details on timestamp offset options below. If Kafka doesn't return the matched offset,
372
372
the query will fail immediately to prevent unintended read from such partition. (This is a kind of limitation as of now, and will be addressed in near future.)<p/>
373
373
<p/>
374
374
Note1: <code>startingTimestamp</code> takes precedence over <code>startingOffsetsByTimestamp</code> and <code>startingOffsets</code>.<p/>
@@ -381,10 +381,10 @@ The following configurations are optional:
<td>none (the value of <code>startingOffsets</code> will apply)</td>
384
+
<td>none (next preference is <code>startingOffsets</code>)</td>
385
385
<td>streaming and batch</td>
386
386
<td>The start point of timestamp when a query is started, a json string specifying a starting timestamp for
387
-
each TopicPartition. Please refer the details on timestamp offset options below. If the matched offset doesn't exist,
387
+
each TopicPartition. Please refer the details on timestamp offset options below. If Kafka doesn't return the matched offset,
388
388
the query will fail immediately to prevent unintended read from such partition. (This is a kind of limitation as of now, and will be addressed in near future.)<p/>
389
389
<p/>
390
390
Note1: <code>startingOffsetsByTimestamp</code> takes precedence over <code>startingOffsets</code>.<p/>
@@ -413,8 +413,8 @@ The following configurations are optional:
413
413
<td>none (next preference is <code>endingOffsetsByTimestamp</code>)</td>
414
414
<td>batch query</td>
415
415
<td>The end point when a batch query is ended, a json string specifying an ending timestamp for
416
-
all partitions in topics being subscribed. Please refer the details on timestamp offset options below. If the matched offset doesn't exist, the offset will
417
-
be set to latest.<p/>
416
+
all partitions in topics being subscribed. Please refer the details on timestamp offset options below.
417
+
If Kafka doesn't return the matched offset, the offset will be set to latest.<p/>
418
418
Note: <code>endingTimestamp</code> takes precedence over <code>endingOffsetsByTimestamp</code> and <code>endingOffsets</code>.<p/>
419
419
</td>
420
420
</tr>
@@ -426,8 +426,8 @@ The following configurations are optional:
426
426
<td>none (next preference is <code>endingOffsets</code>)</td>
427
427
<td>batch query</td>
428
428
<td>The end point when a batch query is ended, a json string specifying an ending timestamp for each TopicPartition.
429
-
Please refer the details on timestamp offset options below. If the matched offset doesn't exist, the offset will
430
-
be set to latest.<p/>
429
+
Please refer the details on timestamp offset options below. If Kafka doesn't return the matched offset,
430
+
the offset will be set to latest.<p/>
431
431
Note: <code>endingOffsetsByTimestamp</code> takes precedence over <code>endingOffsets</code>.
432
432
</td>
433
433
</tr>
@@ -529,7 +529,7 @@ The following configurations are optional:
529
529
### Details on timestamp offset options
530
530
531
531
The returned offset for each partition is the earliest offset whose timestamp is greater than or equal to the given timestamp in the corresponding partition.
532
-
The behavior varies across options if the matched offset doesn't exist - check the description of each option.
532
+
The behavior varies across options if Kafka doesn't return the matched offset - check the description of each option.
533
533
534
534
Spark simply passes the timestamp information to <code>KafkaConsumer.offsetsForTimes</code>, and doesn't interpret or reason about the value.
535
535
For more details on <code>KafkaConsumer.offsetsForTimes</code>, please refer <ahref="https://kafka.apache.org/21/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#offsetsForTimes-java.util.Map-">javadoc</a> for details.
0 commit comments