Feature Request
When configuring DeltaOMS with Unity Catalog support, currently users must specify a storage location (such as S3/ADLS/DBFS) for OMS tables, even if the OMS database is in a UC-managed schema. This is inconvenient and inconsistent with the managed tables model of Unity Catalog, where users only specify the catalog and schema, and UC automatically handles storage locations.
Requested Feature:
- Allow users to configure DeltaOMS by specifying only the UC catalog and schema (e.g.,
catalog.schema), and let UC manage the storage location for OMS tables.
- Remove the requirement to manually set
baseLocation or any location path when deploying OMS in a UC schema.
- OMS initialization should support creating managed tables in UC schemas without explicit location URLs.
Benefits:
- Simplifies and streamlines OMS deployment for Databricks users on Unity Catalog.
- Aligns with Databricks best practices for managed tables in UC.
- Reduces configuration errors and friction when adopting OMS in enterprise environments.
Additional Context:
DeltaOMS v0.7.0-rc1 and earlier still require an external location path, even when using Unity Catalog. This feature request aims to improve native UC integration and reduce manual configuration overhead.
Feature Request
When configuring DeltaOMS with Unity Catalog support, currently users must specify a storage location (such as S3/ADLS/DBFS) for OMS tables, even if the OMS database is in a UC-managed schema. This is inconvenient and inconsistent with the managed tables model of Unity Catalog, where users only specify the catalog and schema, and UC automatically handles storage locations.
Requested Feature:
catalog.schema), and let UC manage the storage location for OMS tables.baseLocationor any location path when deploying OMS in a UC schema.Benefits:
Additional Context:
DeltaOMS v0.7.0-rc1 and earlier still require an external location path, even when using Unity Catalog. This feature request aims to improve native UC integration and reduce manual configuration overhead.