Refer to this topic for information on fixed issues and known limitations associated with Data Catalog.
| Issue | Summary | Workaround | Noted on |
|---|---|---|---|
| View permission requirement | The Manage permission does not implicitly grant View access. Users must have explicit View permission to access or view assets, even if they are authorized to modify them. | Assign both View and Manage permissions to users who require edit capabilities. | May 2026 |
| Domain hierarchical permission propagation | Permission inheritance across domain hierarchies is not currently supported. Permissions assigned at a parent domain level do not propagate to child domains. | Assign permissions explicitly at each required domain level. | May 2026 |
| Asset creator edit permission override | Users who create an asset retain edit permissions for that asset, irrespective of the permissions defined in their assigned roles or policies. This behavior persists until ownership changes or policies are updated. | Periodically review and reassign asset ownership as needed. Incorporate this behavior when defining access control policies. | May 2026 |
| Catalog Metamodel permission configuration visibility | Users with Catalog Metamodel permissions can view all configuration sections under Governance (Business Assets, Technical Assets, Relationships, Models, Predicates), Import, and Catalog (Tag Types), even if they do not have specific management permissions for those resources. Visibility does not guarantee full actionability. | Grant Catalog Metamodel permissions only to users requiring broad configuration visibility. Use role based permissions to restrict modification capabilities where necessary. | May 2026 |
| Profiling fails or runs indefinitely for non-indexed columns in RDBMS datasources | When you enable basic profiling while establishing new RDBMS datasources, profiling jobs that include non-indexed columns may take an extremely long time to complete or run indefinitely. | Configure the metricQueryTimeOut parameter
under the Debugging Parameters section when adding
such datasources. For example, if you set
metricQueryTimeOut value as 300
seconds, the profiling job will
automatically fail if it does not complete within
that time, and a failure message will be displayed
in the UI. |
May 2026 |