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

   ### What changes were proposed in this pull request?
   
   Backport #14530 (merged commit `c150be2456`) to `branch-1.3`, covering 
#14439, #14455, #14458, and #14466.
   
   - Validate namespace names, registration UUIDs, snapshots, schema/partition 
evolution, and default transforms before committing. Preserve staged-create 
validation and accept partition specs without `spec-id`.
   - Return all list results without a page token, serialize direct/staged 
table creation with namespace drop, and make explicit purge clean up reachable 
files while respecting `gc.enabled=false`.
   - Preserve import errors without automatically deleting tables or namespaces.
   
   Resolve conflicts while retaining branch-1.3's scan-filter deserializer, 
deletion-vector checks, audit/ownership updates, and namespace identity 
handling. Adapt the registration test to the OSS JDBC backend's existing 
rejection of overwrite requests.
   
   ### Why are the changes needed?
   
   Bring the consolidated validation, pagination, and purge fixes from #14530 
to the 1.3 release branch.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes, the same behavior changes as #14530: invalid metadata is rejected 
before commit, lists without a token are complete, and import failures do not 
trigger deletion. Explicit purge preserves content files when GC is disabled.
   
   ### How was this patch tested?
   
   - `./gradlew :iceberg:iceberg-common:spotlessApply 
:iceberg:iceberg-rest-server:spotlessApply`
   - `./gradlew :iceberg:iceberg-common:test :iceberg:iceberg-rest-server:test 
-PskipITs`
   - 68 common tests and 485 REST server tests passed, with no failures or 
skips.
   - `git diff --check`
   


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