suxiaogang223 opened a new pull request, #66907:
URL: https://github.com/apache/doris/pull/66907

   ### What problem does this PR solve?
   
   Related PRs: #66809, #66685
   
   `branch-4.1` uses Paimon 1.4.2, but `hive-catalog-shade` 3.1.1 embeds Paimon 
1.3 classes. The existing packaging workaround therefore removes 
`org/apache/paimon/**` and related service descriptors from the shade artifact 
and relies on separately managed Paimon dependencies.
   
   `hive-catalog-shade` 3.1.2 now embeds Paimon 1.4.2, so the workaround is no 
longer needed.
   
   In addition, external table sink hash routing on `branch-4.1` currently uses 
BE execution version 12. Master reserves version 12 for Iceberg Variant 
compatibility and reserves version 13 for external sink hash routing in #66809. 
Release branches must use the same compatibility boundary.
   
   ### What changed?
   
   - Upgrade `hive-catalog-shade` from 3.1.1 to 3.1.2.
   - Remove the dependency-order workaround and the direct 
`paimon-hive-connector-3.1` dependency.
   - Remove the Maven Ant repackaging step that strips `org/apache/paimon/**` 
and Paimon service descriptors.
   - Move external table sink hash routing from BE execution version 12 to 13.
   - Advance the FE and BE maximum execution version to 13 and document 
master's version 12 reservation.
   
   ### Validation
   
   - Verified XML syntax with `xmllint`.
   - Verified Maven dependency resolution includes `hive-catalog-shade:3.1.2` 
and Paimon 1.4.2 modules.
   - Verified the Paimon core and Hive storage-handler classes embedded in 
`hive-catalog-shade:3.1.2` match Paimon 1.4.2.
   - Formatted the changed BE files with clang-format 16.0.6.
   - Ran `git diff --check`.
   - BE compilation was intentionally skipped because this change only updates 
compatibility constants and packaging metadata.
   
   ### Release note
   
   None
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to