You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "L. C. Hsieh (Jira)" <ji...@apache.org> on 2025/08/23 19:13:00 UTC

[jira] [Resolved] (SPARK-53360) Once strategy with ConstantFolding's idempotence should not be broken

     [ https://issues.apache.org/jira/browse/SPARK-53360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

L. C. Hsieh resolved SPARK-53360.
---------------------------------
    Fix Version/s: 4.1.0
                   4.0.1
       Resolution: Fixed

Issue resolved by pull request 52106
[https://github.com/apache/spark/pull/52106]

> Once strategy with ConstantFolding's idempotence should not be broken
> ---------------------------------------------------------------------
>
>                 Key: SPARK-53360
>                 URL: https://issues.apache.org/jira/browse/SPARK-53360
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.1.0, 4.0.0
>            Reporter: L. C. Hsieh
>            Assignee: L. C. Hsieh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.1.0, 4.0.1
>
>
> Currently the optimization rule ConstantFolding is not idempotent. So if the rule is used in any batch with Once strategy, the Once strategy's idempotence will be broken. We encounter this issue.



--
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