[
https://issues.apache.org/jira/browse/SPARK-29835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wenchen Fan resolved SPARK-29835.
---------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 26464
[https://github.com/apache/spark/pull/26464]
> Remove the unnecessary conversion from Statement to LogicalPlan for
> DELETE/UPDATE
> ---------------------------------------------------------------------------------
>
> Key: SPARK-29835
> URL: https://issues.apache.org/jira/browse/SPARK-29835
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Xianyin Xin
> Assignee: Xianyin Xin
> Priority: Major
> Fix For: 3.0.0
>
>
> The current parse and analyze flow for DELETE is: 1, the SQL string will be
> firstly parsed to `DeleteFromStatement`; 2, the `DeleteFromStatement` be
> converted to `DeleteFromTable`. However, the SQL string can be parsed to
> `DeleteFromTable` directly, where a `DeleteFromStatement` seems to be
> redundant.
> It is the same for UPDATE.
--
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
