yuqi1129 opened a new pull request, #14239: URL: https://github.com/apache/gravitino/pull/14239
### What changes were proposed in this pull request? Add the Business Glossary design doc at `design-docs/glossary-design.md`: - **Terms**: terms live under the metalake with no glossary container. Names are unique per metalake. Terms are organized by Domain and by a multi-parent, acyclic broader/narrower hierarchy, plus related terms. - **Domains and bindings**: a term joins domains through an explicit relation, not tags. Term → asset or metric bindings are explicit and never grant access. - **Privileges**: `VIEW_DEFINITION`, `CREATE_DEFINITION` and `MANAGE_DEFINITIONS` on the metalake or a domain, with deny over allow and no self-approval. - **Lifecycle**: `DRAFT` / `APPROVED` / `DEPRECATED` with version history. OSS has no approval workflow; Enterprise plugs one in through an extension point. - **APIs**: REST API, Java/Python clients, a resolve API, CSV import/export, and read-only MCP tools that return approved terms only. ### Why are the changes needed? Gravitino has no way to define business terms and link them to the data that implements them, so agents and users guess what a business word means. This doc settles the design before implementation. Fix: #14238 ### Does this PR introduce _any_ user-facing change? No. Documentation only. ### How was this patch tested? No tests needed; documentation only. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
