You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiao Li (JIRA)" <ji...@apache.org> on 2019/06/04 21:48:00 UTC
[jira] [Resolved] (SPARK-27909) Fix CTE substitution dependence on
ResolveRelations throwing AnalysisException
[ https://issues.apache.org/jira/browse/SPARK-27909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Li resolved SPARK-27909.
-----------------------------
Resolution: Fixed
Assignee: Ryan Blue
> Fix CTE substitution dependence on ResolveRelations throwing AnalysisException
> ------------------------------------------------------------------------------
>
> Key: SPARK-27909
> URL: https://issues.apache.org/jira/browse/SPARK-27909
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.4.3
> Reporter: Ryan Blue
> Assignee: Ryan Blue
> Priority: Major
>
> CTE substitution currently works by running all analyzer rules on plans after each substitution. It does this to fix a recursive CTE case, but this design requires the ResolveRelations rule to throw an AnalysisException when it cannot resolve a table or else the CTE substitution will run again and may possibly recurse infinitely.
> Table resolution should be possible across multiple independent rules. To accomplish this, the current ResolveRelations rule detects cases where other rules (like ResolveDataSource) will resolve a TableIdentifier and returns the UnresolvedRelation unmodified only in those cases.
--
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