Skip to content
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

Open
wants to merge 2 commits into
base: e2e/databricks/parking-sensors-V1
Choose a base branch
from

Conversation

thesqlpro
Copy link
Contributor

@thesqlpro thesqlpro commented Dec 27, 2024

Type of PR

Update to Readme to add Unity Catalog instructions

  • Documentation changes

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

  • No PII in logs
  • Made corresponding changes to the documentation

Validation steps

Issues Closed or Referenced

#978
Following tasks also rely on it
#982
#984
#983
#765

Copy link
Collaborator

@ydaponte ydaponte left a 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.

e2e_samples/parking_sensors/README.md Outdated Show resolved Hide resolved
- *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.
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Unity Catalog] Modify ReadMe to reflect the pre-requisite of having a Regional Metastore
2 participants