laserninja opened a new issue, #13334: URL: https://github.com/apache/gravitino/issues/13334
### Describe the feature Introduce dependency tracking and change-impact analysis so users can preview which consumers a metadata change would affect and optionally reject changes that violate declared compatibility requirements. Start with explicit dependencies from Semantic Models to source tables and columns, establishing a foundation for broader data contracts. ### Motivation A source rename, drop, or schema change can invalidate existing Semantic Models. The current semantic-model design explicitly defers automatic revalidation and cross-catalog impact analysis. Users and AI agents need actionable impact information before executing potentially breaking changes. ### Describe the solution - Persist dependencies between Semantic Models and explicitly referenced source tables and columns, updating them throughout the model lifecycle. - Provide a change-preview API returning affected consumers and compatibility violations, filtered by the caller’s permissions. - Initially support table/column removal, renames, and incompatible column type changes. - Add configurable warn and enforce modes for changes mediated by Gravitino, with revalidation before execution to address concurrent changes. - Detect changes made directly in underlying catalogs through reconciliation, reporting stale or unresolved dependencies. - Expose previews through clients and MCP. Validate with end-to-end cases showing that breaking changes are reported or rejected, compatible changes succeed, and impact reports do not disclose unauthorized metadata. ### Additional context Related to [#12209](https://github.com/apache/gravitino/issues/12209) and `design-docs/gravitino-semantic-model-design.md`. Transitive SQL dependency inference and OpenLineage integration can follow after explicit dependency support. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
