Adding unity catalog skills#62
Open
lopesdiego12 wants to merge 1 commit intodatabricks:mainfrom
Open
Conversation
Author
|
@simonfaltum @lennartkats-db I don't know if I follow all the process to push that PR, can you please review that? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds databricks-unitycatalog, a Unity Catalog governance(parent: databricks-core). This skill focuses on discovering Unity Catalog objects, managing access, and operating UC-governed storage and observability.
Documentation safety checklist
Discovery & inventory
Navigate the 3-level namespace (
catalog.schema.table), list catalogs/schemas/tables via CLI, and search metadata at scale usingsystem.information_schema(tables, columns).Access control
Grant, revoke, and troubleshoot permissions for catalogs, schemas, tables, views, volumes, and external locations. Covers key concepts such as
BROWSEvsSELECT,USE CATALOG/USE SCHEMAtraversal, and ownership vsMANAGE.Volumes & file governance
Use UC managed and external volumes with canonical paths (
/Volumes/<catalog>/<schema>/<volume>/...). Highlights the two-layer permission model for external volumes and the common requirement thatWRITE FILESdepends onREAD FILES.Storage & connections
Work with external locations, storage credentials, and governance patterns, including federation and data sharing concepts.
Lineage & observability
Understand lineage coverage, apply and audit tags, investigate actions via
system.access.audit, and perform cost attribution usingsystem.billing.usage.Operations & migration
Perform maintenance (
OPTIMIZE,VACUUMwith retention and compliance considerations), use time travel, apply constraints, implement cloning strategies, and execute controlled Hive → UC migration workflows.AI/ML objects governance
Apply governance principles to registered models, UC functions as controlled tools, vector search indexes, and feature workflows—avoiding embedding secrets in code.