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

Posted to issues@spark.apache.org by "Xianyin Xin (Jira)" <ji...@apache.org> on 2019/11/11 07:42:00 UTC

[jira] [Updated] (SPARK-29835) Remove the unnecessary conversion from Statement to LogicalPlan for DELETE/UPDATE

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

Xianyin Xin updated SPARK-29835:
--------------------------------
    Summary: Remove the unnecessary conversion from Statement to LogicalPlan for DELETE/UPDATE  (was: Remove the unneeded conversion from Statement to LogicalPlan for DELETE/UPDATE)

> 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
>            Priority: Major
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org