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-532935452 @rdblue I agree with the behavior you posted, but like you said I don't want to mix with SPARK-29014 so I intentionally leave this part unchanged. The current behavior in master branch is: 1. If the identifier starts with a known catalog, use it. This will be a v2 catalog, and the query should be converted to a v2 plan. 2. otherwise, default catalog will be used if it's defined. v2 session catalog will be used if default catalog is not defined. For v2 session catalog, we check the table provider to determine whether to use a v1 plan or a v2 plan. I don't want to change this behavior here, but centralize the code that leads to this behavior. After this refactoring, we can easily change the behavior to what you posted by updating the new extractors I added here.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
