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

   ### What changes were proposed in this pull request?
   
   Backport #13863 to branch-1.3.
   
   - Add `hasInaccessibleTags` and `hasInaccessiblePolicies` to metadata-object 
name and detail list responses.
   - Add backward-compatible Java visibility APIs using `TagList` and 
`PolicyList`, plus the equivalent Python tag APIs.
   - Preserve branch-1.3's direct policy-association APIs while applying 
authorization filtering consistently to direct and inherited associations.
   - Add SDK, authorization, response DTO, OpenAPI, and user-guide coverage.
   
   ### Why are the changes needed?
   
   When all associated tags or policies are inaccessible, an empty list is 
indistinguishable from an object with no associations. The new indicators 
report that associations were omitted without exposing their names, counts, 
details, or inheritance sources.
   
   Fix: #13859
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. Tag and policy list responses expose `hasInaccessibleTags` and 
`hasInaccessiblePolicies`. Java and Python clients add backward-compatible APIs 
that return visible items together with these indicators.
   
   ### How was this patch tested?
   
   - `./gradlew :api:build -x :api:test :clients:client-java:compileTestJava`
   - `./gradlew :clients:client-java:test --tests 
org.apache.gravitino.client.TestSupportTags --tests 
org.apache.gravitino.client.TestSupportPolicies`
   - `python3 -m unittest tests.unittests.test_tag_api` (29 tests passed)
   - `./gradlew :docs:build`
   - Spotless checks
   - Authorization Docker ITs were attempted, but both stopped during Hive 
container initialization because the mapped ports timed out before test 
execution.
   


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