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

   ### Background
   
   Doris links the Paimon and Lance Rust static libraries into the BE. Master 
currently pins paimon-rust 0.5.0-rc1 and builds both libraries with Rust 1.94.0.
   
   ### What problem does this PR solve?
   
   Issue Number: None
   Related PR: #69886 (the write integration can use this dependency after 
adapting to the upstream C APIs)
   PR Type: Release/Dependency
   
   Problem Summary:
   
   Adopt the formal paimon-rust 0.5.0 release, which requires Rust 1.95.0. 
Build Lance with the same toolchain and reject stale installed dependencies so 
an existing compilation image cannot silently keep using the previous artifacts.
   
   ### Details
   
   - **Versions:** paimon-rust 0.5.0-rc1 → 0.5.0; default/minimum Rust 
toolchain for Paimon and Lance 1.94.0 → 1.95.0. Pin the release archive 
checksum and retain locked Cargo builds.
   - **Upstream changes:** The [0.5.0 
release](https://github.com/apache/paimon-rust/releases/tag/v0.5.0) includes 
read compatibility fixes, bounded commit-message range export, pinned Arrow 
schema export, explicit writer close, and retained-input flush accounting. This 
PR consumes the upstream source without a Doris write patch.
   - **Compatibility:** Both Rust static libraries need rebuilding together. 
Installation receipts distinguish the new release/toolchain baseline from older 
prebuilt artifacts. Images that ship only installed dependencies must be 
refreshed; the existing build guard reports this before deleting anything. 
Paimon resolves OpenSSL from the Doris third-party install prefix.
   - **Behavior change:** Native Paimon reads use the 0.5.0 implementation; 
stale installed Rust artifacts require rebuilding.
   - **Rollback:** Revert this dependency change and rebuild both Rust 
libraries together with Rust 1.94.0; replace the Paimon header and archive as a 
pair.
   
   ### Testing
   
   Completed locally on Linux x86_64:
   
   - `python3 thirdparty/test/paimon-build-test.py`: all 28 tests passed, 
including stale installs, failed publication, automatic toolchain selection and 
explicit old-toolchain rejection.
   - The new tests fail against the pre-upgrade build scripts.
   - Built and installed Lance with Rust 1.95.0 and `paimon-c` 0.5.0 with the 
same toolchain, using the existing third-party build entry point and locked 
Cargo dependencies.
   - Linked and called both static libraries from one executable. Read the 
existing Paimon batch-size fixture: verified every key and 128 KiB string 
across all 65 rows and 22 batches. Also checked pinned schema export, 
serializer version 14 and commit-count error handling.
   - The smoke executable has no dynamic OpenSSL dependency; the Paimon build 
selected OpenSSL from this worktree's third-party prefix.
   - `bash -n` on changed shell files and `git diff --check`: passed.
   
   The complete ASAN BE build is in progress. BE unit tests, external 
regression suites and the final production ELF compatibility audit have not 
been completed.
   
   ### Release note
   
   Upgrade the native Paimon dependency to paimon-rust 0.5.0. Building Doris 
now selects Rust 1.95.0 for both Paimon and Lance; older prebuilt third-party 
installations require a rebuild or refreshed compilation image.
   
   ### Check List (For Author)
   
   - Behavior changed: Yes (see Details).
   - Does this need documentation: No new user configuration; the build 
requirement is described above.
   - Pre-submission status: Not ready: complete BE build/CI validation is 
pending; native build and smoke checks passed.
   
   ### AI Disclosure
   
   - Tool: Codex.
   - Generated: dependency/build changes, build-script tests, and this 
description.
   - Human review: Pending author and maintainer review.
   


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