You are viewing a plain text version of this content. The canonical link for it is here.

Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2021/09/20 23:59:44 UTC

[GitHub] [spark] viirya commented on pull request #34030: [SPARK-36790][SQL] Update user-facing catalog to adapt CatalogPlugin

viirya commented on pull request #34030:
URL: https://github.com/apache/spark/pull/34030#issuecomment-923445379


   Having a clean separation between end-user facing catalog and `CatalogPlugin` should be better? I think `CatalogPlugin` is more like a developer-facing API. Some internal stuffs seems not necessary to expose (e.g. FunctionCatalog.loadFunction)?


-- 
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.

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org