You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Data Engineer I would like to use the Unity Catalog on the Parking solution sample so I understand how it works and I don't need to work with the legacy Hive Metastore
DoD
Successfully deploy and configure a Unity Catalog into the E2E Databricks + ADF sample
All the tables should be generated under a "sensordata" metastore
@thesqlpro - @hemaverma told me she is OOF the entire week. Can you please let me know if you will be able to work/finish this during this sprint or if it will spill to the next sprint? Thanks so much!
Some notes from my research thus far:
Since Nov 2023 Unity Catalog is enabled by default (can check using this command in SQL editor SELECT CURRENT_METASTORE();)
Default name for the catalog is the name of the workspace (inherited - although it looks like hyphens are converted to underscores) - this will need to be addressed
Default is in the region the workspace was created (Ex. WS created in EastUS2 then Metastore is in EastUS2)
By default a legacy Hive Metastore exists - will research if this can be removed or not, so far looks like it is included for backward compatibility
As a Data Engineer I would like to use the Unity Catalog on the Parking solution sample so I understand how it works and I don't need to work with the legacy Hive Metastore
DoD
Ensure you've read the Contributing Guide (Microsoft Internal only.)
Top priority
Ready to be picked up when team is available (most probably Sprint 5)
Nice to Have
The text was updated successfully, but these errors were encountered: