[jira] [Commented] (SPARK-28489) KafkaOffsetRangeCalculator.getRanges may drop offsets
[ https://issues.apache.org/jira/browse/SPARK-28489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17145719#comment-17145719 ] Shixiong Zhu commented on SPARK-28489: -- [~klaustelenius] No. The "minPartitions" option for batch queries is added in Spark 3.0. Batch queries before Spark 3.0 will ignore the "minPartitions" option. > KafkaOffsetRangeCalculator.getRanges may drop offsets > - > > Key: SPARK-28489 > URL: https://issues.apache.org/jira/browse/SPARK-28489 > Project: Spark > Issue Type: Bug > Components: Structured Streaming >Affects Versions: 2.4.0, 2.4.1, 2.4.2, 2.4.3 >Reporter: Shixiong Zhu >Assignee: Shixiong Zhu >Priority: Blocker > Labels: correctness, dataloss > Fix For: 2.4.4, 3.0.0 > > > KafkaOffsetRangeCalculator.getRanges may drop offsets due to round off errors. > > This only affects queries using "minPartitions" option. A workaround is just > removing the "minPartitions" option from the query. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-28489) KafkaOffsetRangeCalculator.getRanges may drop offsets
[ https://issues.apache.org/jira/browse/SPARK-28489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17144819#comment-17144819 ] Klaus Telenius commented on SPARK-28489: Does this affect non-structured streaming? > KafkaOffsetRangeCalculator.getRanges may drop offsets > - > > Key: SPARK-28489 > URL: https://issues.apache.org/jira/browse/SPARK-28489 > Project: Spark > Issue Type: Bug > Components: Structured Streaming >Affects Versions: 2.4.0, 2.4.1, 2.4.2, 2.4.3 >Reporter: Shixiong Zhu >Assignee: Shixiong Zhu >Priority: Blocker > Labels: correctness, dataloss > Fix For: 2.4.4, 3.0.0 > > > KafkaOffsetRangeCalculator.getRanges may drop offsets due to round off errors. > > This only affects queries using "minPartitions" option. A workaround is just > removing the "minPartitions" option from the query. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org