jerryshao opened a new pull request, #14522:
URL: https://github.com/apache/gravitino/pull/14522

   ### What changes were proposed in this pull request?
   
   Add `DomainDispatcher` and `DomainManager` for creating, listing, loading, 
altering and deleting domains; managing sub-domains; and publishing or 
unpublishing domains.
   
   Hierarchy and status checks run through the entity store against the locked 
domain state. Register the manager in `GravitinoEnv` and support DOMAIN 
existence checks in `MetadataObjectUtil`.
   
   Stacked on #14496. This draft targets `branch-domain-dev`, so its diff 
includes that dependency until it merges. The 1b-only diff is available in the 
[fork 
comparison](https://github.com/jerryshao/gravitino/compare/13884-domain-store-1a...13884-domain-manager-1b).
   
   ### Why are the changes needed?
   
   Provide the server-side domain operations for #13884 while keeping the 
hierarchy one level deep and published sub-domains under published parents.
   
   Part of #13884. Backing-tag creation and binding, authorization, hooks, 
events and draft visibility filtering follow in separate PRs. Creation paths 
include TODOs for the backing-tag work.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No REST or client API changes. This adds internal server operations.
   
   ### How was this patch tested?
   
   - H2-backed manager tests cover domain operations, hierarchy and status 
rules, moves and no-op cases.
   - Mock-store tests cover exception mapping and the checks passed to locked 
store operations.
   - `./gradlew compileJava compileTestJava spotlessCheck -PskipITs`
   - `./gradlew :core:javadoc` (run separately)
   - Related tests through `:core:coreUnitTest` and `:core:coreH2Test`.
   
   MySQL and PostgreSQL tests run in CI.
   


-- 
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]

Reply via email to