So this one goes on my wishlist for Databricks Unity Catalog:
I am missing one feature in the recently introduced BROWSE permission in Databricks Unity Catalog.
The BROWSE permission allows users to see all the metadata in a catalog without exposing data. Thus the user is able to see all schemas, tables, views and other UC objects, but not their contents. While I find this approach very helpful, since you can only ask permission for things you know that they exist, I would like to have some more granular control.
A BROWSE permission on the schema level would enable more control for the admins to expose metadata to users. An example would be a schema containing technical information e.g. from data pipelines. Even only the metadata could confuse users.
I don’t believe Santa will do me the favor, so my wish goes to Databricks: the BROWSE permissions is very cool and would be even better when it could also be applied on the schema level.
