This is an automated email from the ASF dual-hosted git repository.

Gabriel39 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/doris.git


The following commit(s) were added to refs/heads/master by this push:
     new da4f490ae07 [chore](build) Update lance-c to include runtime BTree 
selection (#69643)
da4f490ae07 is described below

commit da4f490ae076e00aba89ff92bc8928c998d65fbc
Author: Gabriel <[email protected]>
AuthorDate: Tue Oct 27 09:38:27 2026 +0800

    [chore](build) Update lance-c to include runtime BTree selection (#69643)
    
    ### What problem does this PR solve?
    
    Related PR: https://github.com/lance-format/lance-c/pull/98
    
    Problem Summary: Update lance-c from
    `4fafcd64525b274b113208390bbcca86bbbc093b` to the merged upstream main
    commit `a51ab47a9c814a746cb1714c99fad93dd3a188b8`, and refresh the
    source archive name and MD5. This brings in the opt-in runtime BTree
    segment selector and its pre-decode memory guards. Existing master
    callers retain their selection behavior because the new native option
    defaults to false. The existing Foyer patch applies without changes and
    with zero fuzz.
    
    ### Release note
    
    None. This updates the dependency; it does not enable the new opt-in
    native feature in Doris.
    
    ### Validation
    
    - Verified the downloaded immutable source archive's MD5 and applied the
    existing Foyer patch with zero fuzz. The same patch is used on master
    and branch-4.2.
    - `cargo test --offline --locked` on that patched source: 515 tests
    passed, including 82 unit tests and 385 C API tests. The normal command
    ignores three C/C++ executable compilation tests.
    - C and C++ API test sources passed syntax-only compilation against the
    new patched headers.
    - Exercised the existing source-patching block for first application, a
    cached no-op, and stale-checksum re-extraction; verified resulting
    source equality.
    - Shell syntax and staged whitespace checks passed. Full Doris BE
    build/integration validation remains for CI.
    
    ### Check List (For Author)
    
    - Test
        - [x] Unit Test
    - [x] Manual test: source checksum/patch lifecycle and C/C++ header
    compatibility checks above.
        - [ ] Regression test
    - Behavior changed:
    - [x] No. Existing Doris callers do not enable the new native option.
    - Does this need documentation?
        - [x] No. No Doris configuration or user interface changes.
    
    ### Check List (For Reviewer who merge this PR)
    
    - [ ] Confirm the release note
    - [ ] Confirm test cases
    - [ ] Confirm document
    - [ ] Add branch pick label
---
 thirdparty/vars.sh | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/thirdparty/vars.sh b/thirdparty/vars.sh
index 347f2b0fd7d..027fe6f6523 100644
--- a/thirdparty/vars.sh
+++ b/thirdparty/vars.sh
@@ -617,11 +617,11 @@ PUGIXML_SOURCE=pugixml-1.15
 PUGIXML_MD5SUM="3b894c29455eb33a40b165c6e2de5895"
 
 # lance-c
-# Includes lance-c #97: resolve index/column name collisions without 
serializing prewarm.
-LANCE_C_DOWNLOAD="https://codeload.github.com/lance-format/lance-c/tar.gz/4fafcd64525b274b113208390bbcca86bbbc093b";
-LANCE_C_NAME="lance-c-4fafcd64525b274b113208390bbcca86bbbc093b.tar.gz"
-LANCE_C_SOURCE="lance-c-4fafcd64525b274b113208390bbcca86bbbc093b"
-LANCE_C_MD5SUM="65e924fb62137c5dd4d58af3fb33923a"
+# Includes lance-c #98: bounded runtime BTree segment selection with 
decoded-memory guards.
+LANCE_C_DOWNLOAD="https://codeload.github.com/lance-format/lance-c/tar.gz/a51ab47a9c814a746cb1714c99fad93dd3a188b8";
+LANCE_C_NAME="lance-c-a51ab47a9c814a746cb1714c99fad93dd3a188b8.tar.gz"
+LANCE_C_SOURCE="lance-c-a51ab47a9c814a746cb1714c99fad93dd3a188b8"
+LANCE_C_MD5SUM="d1282cff3d63acfc0450db1f00d6ab6f"
 
 # paimon-rust
 
PAIMON_RUST_DOWNLOAD="https://github.com/apache/paimon-rust/archive/refs/tags/v0.4.0-rc1.tar.gz";


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

Reply via email to