rdblue commented on pull request #31541: URL: https://github.com/apache/spark/pull/31541#issuecomment-780695747
@cloud-fan, Russell is right. We allow extending `spark_catalog` to layer on more functionality, while still being able to load and use v1 tables. Any validation that is specific to `spark_catalog` should be done there, not in the planner. That's just basic good design and separation of concerns. In addition, getting this wrong is needlessly limiting. Russell's case is a great example of that, where you can't really augment `spark_catalog` in certain ways, like supporting namespaces that have additional nesting. ---------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
