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

   ### What changes were proposed in this pull request?
   
   Make `USE_SEMANTIC_MODEL` the preferred privilege for discovering semantic 
models and loading their definitions. Retain `SELECT_SEMANTIC_MODEL` and its 
Java helper as deprecated aliases with the same permission bit, using the 
existing compatibility map for authorization and revocation.
   
   Add `SKIP_APPLY_PRIVILEGES` for connector callback selection and privilege 
filtering, separate from the semantic-model privilege set used for catalog-type 
validation. Update authorization expressions, OpenAPI, documentation, and tests.
   
   ### Why are the changes needed?
   
   Addresses the post-merge review on #12867: align the privilege name with 
`USE_MODEL` and give connector exclusions a dedicated constant that can include 
other privileges. Related to #12594.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Clients can grant `USE_SEMANTIC_MODEL` and use 
`Privileges.UseSemanticModel`. Existing grants and callers using 
`SELECT_SEMANTIC_MODEL` remain supported. The privilege does not authorize 
access to underlying source data.
   
   ### How was this patch tested?
   
   - 83 focused tests passed on JDK 17 across API, core, server-common, and 
server. Coverage includes privilege parsing and binding, H2 persistence, mixed 
connector grants, old/new-name revocation, and authorization expressions.
   - `./gradlew spotlessApply`, `./gradlew :docs:build`, and 
API/core/server-common Javadoc tasks passed. Javadoc emitted existing warnings 
in unrelated files.
   - Standards and specification reviews found no actionable issues.
   
   Docker integration suites were not run.
   


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