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

Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:25:23 UTC

[jira] [Updated] (SPARK-17482) Analyzer should be able run on top of optimized rule

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

Hyukjin Kwon updated SPARK-17482:
---------------------------------
    Labels: bulk-closed  (was: )

> Analyzer should be able run on top of optimized rule
> ----------------------------------------------------
>
>                 Key: SPARK-17482
>                 URL: https://issues.apache.org/jira/browse/SPARK-17482
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Davies Liu
>            Priority: Major
>              Labels: bulk-closed
>
> Right now, analyzer has some assumption that the query came from parser or DataFrame operations (or analyzed), optimizer may break these assumption. It may process wrong answer if ran analyzer on a optimized logical plan.
> In long term, the analyzer rules should not have these assumption, it should still produce correct result whenever it's optimized or not. We should have unit test to ensure that.
> This may depends on how large the change needed to meet this requirement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org