ODIn/spark-instrumented-optimizer
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

[SPARK-35611][SS][FOLLOW-UP] Improve the user guide document

Browse source 
### What changes were proposed in this pull request?
Improve the user guide document.

### Why are the changes needed?
Make the user guide clear.

### Does this PR introduce _any_ user-facing change?
No.

### How was this patch tested?
Doc change only.

Closes #33854 from xuanyuanking/SPARK-35611-follow.

Authored-by: Yuanjian Li <yuanjian.li@databricks.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
(cherry picked from commit dd3f0fa8c2)
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
This commit is contained in:
Yuanjian Li 2021-08-27 10:27:06 +09:00 committed by Hyukjin Kwon
parent 069f326e36
commit f50f2d474c
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/structured-streaming-kafka-integration.md
View file

@ -547,10 +547,10 @@ The following configurations are optional:
<td>"error" or "latest"</td>
<td>"error"</td>
<td>streaming and batch</td>
<td>Defines the behavior when the starting offset by timestamp is specified (either global or per partition), and Kafka doesn't return the matched offset.<p/>
<td>The strategy will be used when the specified starting offset by timestamp (either global or per partition) doesn't match with the offset Kafka returned. Here's the strategy name and corresponding descriptions:<p/>
<p/>
"error": fail the query.<p/>
"latest": set the offset to the latest, so that further new records in the partition are being read.<p/></td>
"error": fail the query and end users have to deal with workarounds requiring manual steps.<p/>
"latest": assigns the latest offset for these partitions, so that Spark can read newer records from these partitions in further micro-batches.<p/></td>
</tr>
</table>