Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14397
@dongjoon-hyun
#### New behavior versus existing systems
I was not talking about recursive CTE's (which can be very useful in some
cases). We are changing the behavior of the Analyzer, and this might surprise
users. I would like to know if there is a common approach to this among other
systems; so we can justify the change in behavior.
#### Resolve Relations
The change you propose is almost subsuming the `ResolveRelations` rule. I
think it is correct to to do this. However I am not a big fan of duplicating
the behavior in two rules. Do you think there is way to get around this? Could
we for instance centralize the logic in `ResolveRelations`?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
