[
https://issues.apache.org/jira/browse/SPARK-30658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17027907#comment-17027907
]
Tathagata Das commented on SPARK-30658:
---------------------------------------
Fixed in this PR https://github.com/apache/spark/pull/27373
> Limit after on streaming dataframe before streaming agg returns wrong results
> -----------------------------------------------------------------------------
>
> Key: SPARK-30658
> URL: https://issues.apache.org/jira/browse/SPARK-30658
> Project: Spark
> Issue Type: Bug
> Components: Structured Streaming
> Affects Versions: 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.2,
> 2.4.3, 2.4.4
> Reporter: Tathagata Das
> Assignee: Tathagata Das
> Priority: Critical
> Fix For: 3.0.0
>
>
> Limit before a streaming aggregate (i.e. {{df.limit(5).groupBy().count()}})
> in complete mode was not being planned as a streaming limit. The planner rule
> planned a logical limit with a stateful streaming limit plan only if the
> query is in append mode. As a result, instead of allowing max 5 rows across
> batches, the planned streaming query was allowing 5 rows in every batch thus
> producing incorrect results.
--
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
