HeartSaVioR commented on pull request #31541: URL: https://github.com/apache/spark/pull/31541#issuecomment-780899808
So I'm confused again - the R&R of "session catalog" doesn't seem to be agreed upon. Still something I don't understand is, why it has to be session catalog? Can your case be solved on custom catalog instead? I got a feeling there're reasons you have to extend spark_catalog instead of picking another catalog, which sounds like "lacks" of custom catalog and we may be able to just address the lacks in custom catalog, instead of trying to modify "reserved" one. (Probably if the name of session catalog was "v1_catalog" to give best clarity then no one would try to use it for v2.) ---------------------------------------------------------------- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
