You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Gengliang Wang (Jira)" <ji...@apache.org> on 2026/03/05 04:05:00 UTC

[jira] [Resolved] (SPARK-55695) Avoid double planning in row-level operations

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

Gengliang Wang resolved SPARK-55695.
------------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

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

> Avoid double planning in row-level operations
> ---------------------------------------------
>
>                 Key: SPARK-55695
>                 URL: https://issues.apache.org/jira/browse/SPARK-55695
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.1.0, 4.0.0, 4.1.1
>            Reporter: Anton Okolnychyi
>            Assignee: Anton Okolnychyi
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> We must avoid double planning in DELETE, UPDATE, MERGE operations.



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