+1 for the proposal. The current behavior is confusing.
We also came up with another case that we should consider while
implementing a ViewCatalog: an unresolved relation in a permanent view
(from a view catalog) should never resolve a temporary table. If I have a
view `pview` defined as `select
+1, I think it's good for both end-users and Spark developers:
* for end-users, when they lookup a table, they don't need to care which
command triggers it, as the behavior is consistent in all the places.
* for Spark developers, we may simplify the code quite a bit. For now we
have two code paths
Hi all,
As discussed in SPARK-29900, Spark currently has two different relation
resolution behaviors:
1. Look up temp view first, then table/persistent view
2. Look up table/persistent view
The first behavior is used in SELECT, INSERT and a few commands that
support temp views such as
