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

   ### What changes were proposed in this pull request?
   
   Replace #14543 with a clean backport to `branch-1.3`, containing exactly 
three cherry-picked main commits:
   
   - #14491: `89a71fe4811fbaa8e0380098f0382dba13e6cffb`
   - #14527: `207972fe44a95a42ebbffe68d12cdc51d2649230`
   - #14528: `27201d342e6e289db00dda8a639da01c1f49d82b`
   
   Original authors and source-SHA trailers are preserved. Necessary 1.3 
compatibility adjustments are included in the corresponding commits. The final 
tree exactly matches merging #14543 into the current target branch; no 
intermediate development or provenance-only commits are included.
   
   ### Why are the changes needed?
   
   Keep the same PostgreSQL identifier/schema safeguards, Spark write 
validation and Trino rollback cleanup while making the backport history 
straightforward to review.
   
   ### Does this PR introduce _any_ user-facing change?
   
   The same fixes as #14543: safe native PostgreSQL identifiers and generated 
indexes; copied schema identity rejection; conservative non-empty schema drop 
refusal; early rejection of unsupported Spark PostgreSQL writes; and native 
Trino transaction rollback cleanup. No new configuration or storage migration.
   
   ### How was this patch tested?
   
   133 targeted cases passed on this head, with no failures or skips:
   
   - PostgreSQL: 91 tests, Docker enabled.
   - Core schema/identifier/name-normalization: 28 tests.
   - Spark common/3.3/3.4/3.5 write validation: 2 tests each.
   - Trino transaction rollback: 3 tests.
   - Schema ID collision: 3 tests, covering H2/MySQL/PostgreSQL.
   
   Spotless, diff checks and `./gradlew :docs:build` passed. An independent 
cumulative review found no outstanding findings. No full core suite or deployed 
end-to-end test was 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