You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Terry Kim (Jira)" <ji...@apache.org> on 2021/09/28 01:52:00 UTC
[jira] [Comment Edited] (SPARK-36586) Migrate all ParsedStatement
to the new v2 command framework
[ https://issues.apache.org/jira/browse/SPARK-36586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17421106#comment-17421106 ]
Terry Kim edited comment on SPARK-36586 at 9/28/21, 1:51 AM:
-------------------------------------------------------------
[~cloud_fan] totally missed this ping (never got an email notification). :) Looks like the work has started and I will also chip in. Thanks!
was (Author: imback82):
[~cloud_fan] totally missed this ping. :) Looks like the work has started and I will also chip in. Thanks!
> Migrate all ParsedStatement to the new v2 command framework
> -----------------------------------------------------------
>
> Key: SPARK-36586
> URL: https://issues.apache.org/jira/browse/SPARK-36586
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.3.0
> Reporter: Wenchen Fan
> Priority: Major
>
> The ParsedStatement needs to be pattern matched in two analyzer rules and results to a lot of duplicated code.
> The new v2 command framework defines a few basic logical plan nodes such as UnresolvedTable, and we only need to resolve these basic nodes, and pattern match v2 commands only once in the rule `ResolveSessionCatalog` for v1 command fallback.
> We should migrate all the ParsedStatement to v2 command framework.
--
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