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

   ### What changes were proposed in this pull request?
   
   Extract the runtime fixes and regression tests from #12954:
   
   - Reject Arrow streams containing rows before CreateTable changes metadata 
or storage, including exist_ok and overwrite requests.
   - Map backend authentication/authorization failures to Lance HTTP 401/403 
without stack traces, and remove stack traces from auxiliary authorization 
denials.
   - Return a generic HTTP 500 response for unexpected failures while retaining 
server-side logging.
   
   ### Why are the changes needed?
   
   CreateTable silently discards supplied rows, while backend access failures 
become HTTP 500 and error responses can expose internal details. Keeping these 
fixes separate lets #12954 focus on authentication documentation.
   
   Fix: #12988
   
   ### Does this PR introduce _any_ user-facing change?
   
   Nonempty CreateTable streams return HTTP 406 before mutation. Backend 
authentication/authorization failures retain HTTP 401/403. Unexpected HTTP 500 
responses no longer expose exception messages or stack traces. No configuration 
keys or identity propagation behavior change.
   
   ### How was this patch tested?
   
   185 tests passed: 166 unit tests across lance-common and lance-rest-server, 
plus 19 integration tests in LanceNamespaceAuthorizationIT, 
LanceTableAuthorizationIT, and LanceRESTServiceAuthIT.
   
   Coverage includes Arrow batches, create/overwrite side effects, error 
response sanitization, and standalone backend denial through a separate 
production server JVM. Relevant Spotless formatting tasks passed. Integration 
tests used the embedded backend; Docker and the full deployment matrix 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