cloud-fan commented on issue #25747: [SPARK-29039][SQL] centralize the catalog and table lookup logic URL: https://github.com/apache/spark/pull/25747#issuecomment-535328323 Hi @rdblue , thanks for the review! I tried your idea to use `UnresovledRelation` to separate catalog and table resolution completely, but I can't make it work as I explained in https://github.com/apache/spark/pull/25747#discussion_r328421165 In fact, the previous code also resolves catalog and table together: https://github.com/apache/spark/pull/25747/files#diff-57b3d87be744b7d79a9beacf8e5e5eb2L960 This PR focuses on centralizing the catalog/table resolving logic. I think it's possible to separate catalog and table resolution completely, but it needs more significant refactor, e.g. adding intermediate logical plans to represent statements with catalog resolved.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
