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

   ### What problem does this PR solve?
   
   Issue Number: None
   
   Related PR: #62689
   
   Problem Summary: This PR is a review-focused pick of the JNI writer portion 
from apache/doris#62689 onto master. It adds the Paimon external table INSERT 
planning path, transaction and commit-message plumbing, Thrift 
sink/query-option fields, BE pipeline sink operator, JNI Arrow IPC writer 
bridge, and Java `PaimonJniWriter`.
   
   The paimon-cpp native writer, bucket-shuffle/native partition writer path, 
thirdparty paimon-cpp changes, and regression tests are intentionally excluded 
so reviewers can focus on the JNI write path.
   
   Original PR: https://github.com/apache/doris/pull/62689
   Original PR title: `[feat](paimon) support paimon insert by jni&paimon-cpp`
   Original author: `lvliangliang <[email protected]>`
   
   ### Release note
   
   Support Paimon INSERT through the JNI writer path.
   
   ### Check List (For Author)
   
   - Test: Manual test
       - `mvn -f fe/pom.xml package -pl be-java-extensions/paimon-scanner -am 
-Drevision=1.2-SNAPSHOT -DskipTests -Dskip.doc=true -Dcheckstyle.skip=true -T 1`
       - `git diff --check HEAD`
       - Ran clang-format v16 on touched BE C++ files through Doris 
build-support formatter
       - Attempted `mvn -f fe/pom.xml package -pl fe-core -am 
-Drevision=1.2-SNAPSHOT -DskipTests -Dskip.doc=true -Dcheckstyle.skip=true -T 
1`; it failed in existing parser generated-source mismatches unrelated to the 
Paimon pick (`LogicalPlanBuilder` HOT/onTablesClause/routine load label symbols)
   - Behavior changed: Yes. Paimon external table INSERT can be planned and 
executed through JNI writer.
   - Does this need documentation: Yes. Follow-up docs may be needed for 
user-visible Paimon INSERT support.


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