You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/05/31 09:08:00 UTC
[jira] [Updated] (SPARK-48481) OptimizeOneRowPlan should not be effective for streaming DataFrame
[ https://issues.apache.org/jira/browse/SPARK-48481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated SPARK-48481:
-----------------------------------
Labels: pull-request-available (was: )
> OptimizeOneRowPlan should not be effective for streaming DataFrame
> ------------------------------------------------------------------
>
> Key: SPARK-48481
> URL: https://issues.apache.org/jira/browse/SPARK-48481
> Project: Spark
> Issue Type: Bug
> Components: Optimizer, Structured Streaming
> Affects Versions: 4.0.0, 3.5.2, 3.4.4
> Reporter: Jungtaek Lim
> Priority: Major
> Labels: pull-request-available
>
> This bug is introduce from Apache Spark 3.3.0.
> OptimizeOneRowPlan aggressively rewrites operators or removes operators if the rule figures out that the operator has a chance to be optimized with the stats that there will be max 1 row in the input.
> This is problematic for streaming, because we aren't seeing the whole data but a part of data in the current microbatch and optimizer is not aware of this.
> There are various viable approaches to deal with, but maybe fixing the rule to disable this effectively with streaming DataFrame would have least effect.
> (There is a separate wider effort to achieve better stability between QO and streaming. Since it would take a considerable time, we still need point fixes during the time.)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org