[ 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org