-
Notifications
You must be signed in to change notification settings - Fork 475
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Unity Catalog] - Update Readme for Unity Catalog (#978) #996
base: e2e/databricks/parking-sensors-V1
Are you sure you want to change the base?
[Unity Catalog] - Update Readme for Unity Catalog (#978) #996
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's have a call on the PRs when you start your day. I would like to have an unique PR as it would be much easier to test and it is a better way to keep related changes together.
- *Permissions needed*: If a regional metastore does not exist then an account admin must create one. [Metastore Creation](https://learn.microsoft.com/en-us/azure/databricks/data-governance/unity-catalog/create-metastore) | ||
- *Permissions needed*: Once the catalog is created, the following permissions must be granted to *All account users* in order to run the notebooks *02_standardize.py* and *03_tranfsorm.py*. | ||
- USE CATALOG, USE SCHEMA, CREATE TABLE, MODIFY, SELECT | ||
- Alternatively these permissions can be given to the MSI generated for the Databricks Linked Service in ADF. This is the recommended approach and a better security practice. However since a separate catalog is created for this demo environment, granting privelages to *All account users* is a potential work around as many of the APIs for managing Unity Catalog are still being developed as of the writing of these instructions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Related with the previous point, you mention now that a separate catalog is created for this demo environment - where is this being created? In the setup notebook you mention "Use the Sensor Catalog Created in the Prerequisites " - so in the prerequisites you are generally asking to follow the instructions to create the "Unity Catalog", but I was expecting that the metastore regional piece was manual and the catalog could be added to the automation. On a second note - maybe the ReadMe needs to go together with the code changes when they are ready.
Type of PR
Update to Readme to add Unity Catalog instructions
Purpose
Unity Catalog is a new addition to this repo. By default it is added to all new Databricks workspaces. This documentation addition allows users of the repo to create a metastore and catalog for this sample.
Author pre-publish checklist
Validation steps
Issues Closed or Referenced
#978
Following tasks also rely on it
#982
#984
#983
#765