rdblue commented on issue #25747: [SPARK-29039][SQL] centralize the catalog and table lookup logic URL: https://github.com/apache/spark/pull/25747#issuecomment-536030931 @cloud-fan, we could add `UnresolvedV2Table`, but I don't think that's very valuable. Looking up whether a catalog exists is checking a hashmap, so it's cheap and we don't mind doing it twice. I'm not sure from your last comment whether we agree on what the future should be, but I think we are close to agreement. Catalog resolution and table resolution should be separate. When we have a v2 catalog that isn't the session catalog, we should always convert to a v2 plan. We only need to look up the table and mix that logic together for v1, in `DataSourceResolution`.
---------------------------------------------------------------- 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]
