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

   ### What problem does this PR solve?
   
   This PR fixes all JNI-related To Do items under the DORIS-27038 epic:
   
   - DORIS-27053: keep Paimon C++ splits on the legacy scanner until 
FileScannerV2 can dispatch them.
   - DORIS-27058: honor query cancellation while JNI batches are fully filtered.
   - DORIS-27059: make JNI open/close cleanup exception-safe and avoid marking 
a failed close complete.
   - DORIS-27064: propagate adaptive batch-size updates to open JNI scanners 
and Paimon/Hudi hybrid children.
   - DORIS-27077: preserve end-of-split state so repeated reads after scanner 
close are idempotent.
   - DORIS-27078: retain split-level Paimon options and Hadoop configuration as 
rolling-upgrade fallbacks.
   
   Issue Number: DORIS-27053, DORIS-27058, DORIS-27059, DORIS-27064, 
DORIS-27077, DORIS-27078
   
   Related PR: N/A
   
   ### Release note
   
   Harden JNI table-reader lifecycle handling and rolling-upgrade compatibility 
for Paimon and Hudi scans.
   
   ### Check List
   
   - [x] Added comments for scanner-selection, lifecycle, adaptive-batch, and 
compatibility invariants.
   - [x] Added focused unit tests covering cancellation, EOF idempotence, 
cleanup failure, adaptive batching, scanner selection, and Paimon fallback 
precedence.
   - [x] Passed 45 focused ASAN BE unit tests from 7 suites.
   - [x] Passed `build-support/check-format.sh` and `git diff --check`.
   - [x] Ran changed-file clang-tidy; analysis is blocked by the existing 
toolchain missing `stddef.h` and pre-existing repository diagnostics.
   


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