[
https://issues.apache.org/jira/browse/SPARK-25005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637560#comment-16637560
]
Quentin Ambard commented on SPARK-25005:
----------------------------------------
ok I see, great idea, and the consumer ensure us that the position won't be
updated if pool returns an empty list for any reason?
Also if a partition is full with invisible messages due to transaction abort,
we'll have to wait for the pool timeout everytime (at least that's what I see
in my tests) It could hurt throughput, especially if we have to wait for each
partition. Not sure how we could solve that...
> Structured streaming doesn't support kafka transaction (creating empty offset
> with abort & markers)
> ---------------------------------------------------------------------------------------------------
>
> Key: SPARK-25005
> URL: https://issues.apache.org/jira/browse/SPARK-25005
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.3.1
> Reporter: Quentin Ambard
> Assignee: Shixiong Zhu
> Priority: Major
> Fix For: 2.4.0
>
>
> Structured streaming can't consume kafka transaction.
> We could try to apply SPARK-24720 (DStream) logic to Structured Streaming
> source
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
