[
https://issues.apache.org/jira/browse/SPARK-22486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248891#comment-16248891
]
Cody Koeninger commented on SPARK-22486:
----------------------------------------
Can you identify a clear use case for this, given that
- applications have to be tolerant of repeated messages anyway
- the consumer doing the work (on the executor) is not the same as the consumer
doing the coordination and offset commits (on the driver)
> Support synchronous offset commits for Kafka
> --------------------------------------------
>
> Key: SPARK-22486
> URL: https://issues.apache.org/jira/browse/SPARK-22486
> Project: Spark
> Issue Type: Improvement
> Components: DStreams
> Affects Versions: 2.2.0
> Reporter: Jeremy Beard
>
> CanCommitOffsets provides asynchronous offset commits (via
> Consumer#commitAsync), and it would be useful if it also provided synchronous
> offset commits (via Consumer#commitSync) for when the desired behavior is to
> block until it is complete.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
