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

   ### What changes were proposed in this pull request?
   
   Reject omitted/null inUse before enabling or disabling catalogs and 
metalakes while preserving the existing public boolean constructor/getter 
signatures. Validate null property values and array/update elements at the 
request boundary. Normalize explicit JSON null column defaults to the existing 
unset-default sentinel.
   
   ### Why are the changes needed?
   
   Malformed requests can silently disable metadata containers or return HTTP 
500. Validation should reject them before dispatch and report HTTP 400. JSON 
and builder defaults should agree.
   
   Fix: #14580
   
   ### Does this PR introduce _any_ user-facing change?
   
   Missing/null required fields are rejected. Explicit true/false and valid 
requests retain their behavior. Nullable optional containers remain accepted. 
Explicit SQL NULL defaults remain distinct from unset defaults. No metadata 
schema, dependency, or public method signature changes.
   
   ### How was this patch tested?
   
   - Added JSON-deserialization regression coverage; the original code failed 
the new invalid-input cases.
   - 458 common DTO tests and all 30 
TestCatalogOperations/TestMetalakeOperations REST tests passed.
   - REST tests verify HTTP 400 and no enable/disable invocation for 
omitted/null states, plus the existing explicit true/false paths.
   - Property tests cover all seven create request types with valid values, 
null containers, and invalid null values.
   - Module Spotless checks and git diff --check passed.
   - Live backend integration tests 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