[fix](build) Keep Arrow 17 and 24 in shared thirdparty - #66546
Open
hubgeter wants to merge 2 commits into
Open
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
### What problem does this PR solve? Issue Number: None Related PR: apache#66221 Problem Summary: master and branch-4.1 consume the same prebuilt thirdparty prefix. Upgrading the unversioned Arrow/Paimon stack to Arrow 24 makes unchanged branch-4.1 compile against incompatible headers and libraries. Keep Arrow 17/Paimon 17 in the legacy unversioned prefix, install Arrow 24/Paimon 24 in a versioned prefix selected by master, build and validate both source closures independently, and recover only stale stacks. ### Release note None ### Check List (For Author) - Test: - Manual test: built Arrow/Paimon 17 and Arrow/Paimon 24 thirdparty stacks - Manual test: ran thirdparty/test/arrow-paimon-lifecycle-test.sh - Manual test: ran build-support/check-format.sh - Partial build check: configured ASAN BE and compiled 13,378 of 14,456 targets without errors before stopping at the user's request - Behavior changed: Yes. The shared thirdparty prefix keeps Arrow/Paimon 17 at the legacy root and installs master's Arrow/Paimon 24 under a versioned directory. - Does this need documentation: No
hubgeter
force-pushed
the
worktree/dual-arrow-17-24
branch
from
August 7, 2026 07:09
77cf9ff to
8a5c653
Compare
Contributor
Author
|
run buildall |
Contributor
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
### What problem does this PR solve? Issue Number: None Related PR: apache#66221 Problem Summary: External regression replaces the standard FE configuration with its own fe.conf. That override omitted arrow.adbc.driver.jni.library.path, so the ADBC connector extracted the JNI library bundled in the Maven JAR instead of loading the compatible library built and packaged by Doris thirdparty. On older TeamCity hosts, every Flight SQL catalog case then failed while initializing JniLoader because the bundled library requires newer GLIBC and GLIBCXX versions. Keep the external regression JVM options aligned with the standard FE configuration so it loads output/fe/lib/libadbc_driver_jni.so. ### Release note None ### Check List (For Author) - Test: - Manual test: verified the JDK 17 option expands arrow.adbc.driver.jni.library.path to the configured DORIS_HOME lib directory - Manual test: verified the packaged thirdparty JNI library is present - Manual test: git diff --cached --check - Behavior changed: No. This only corrects the External Regression FE startup configuration. - Does this need documentation: No
Contributor
Author
|
run buildall |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
Related PR: #66221
Problem Summary: master and branch-4.1 consume the same prebuilt thirdparty prefix. Upgrading the unversioned Arrow/Paimon stack to Arrow 24 makes unchanged branch-4.1 compile against incompatible headers and libraries. Keep Arrow 17/Paimon 17 in the legacy unversioned prefix, install Arrow 24/Paimon 24 in a versioned prefix selected by master, build and validate both source closures independently, and recover only stale stacks.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)