branch-4.1:[refactor](thirdparty) Align Arrow upgrade with standard thirdparty workflow - #67437
Draft
hubgeter wants to merge 1 commit into
Draft
Conversation
…orkflow ### What problem does this PR solve? Issue Number: None Related PR: apache#66221, apache#66480 Problem Summary: The branch-4.1 Arrow 24 backport inherited an Arrow/Paimon-specific semantic-fingerprint system, installed-artifact validators, focused recovery paths, and dedicated lifecycle CI. This diverged from the standard Doris thirdparty workflow and made dependency maintenance unnecessarily complex. Follow the existing model used by other dependency upgrades: keep source versions and checksums in vars.sh, use patch markers for source preparation, rely on matching prebuilts, and use the existing platform completion sentinel for full rebuilds. The branch-4.1 BE unit-test entrypoint still supports an older install-only build image, so retain only a lightweight libarrow_compute.a check that stages and installs the shared complete prebuilt when needed. ### Release note None ### Check List (For Author) - Test: Manual test - Bash syntax checks for all changed shell scripts - YAML parsing for the changed GitHub workflow - Branch-4.1 thirdparty download, ADBC, and Paimon codec tests - Clean Arrow/Paimon/xsimd/Brotli download and patch application - Repeated download for idempotence and Paimon patch-marker migration - ShellCheck with error severity and git diff --check - Full thirdparty compilation was not run - Behavior changed: Yes. Arrow/Paimon now use the standard matching-prebuilt and full-rebuild workflow; the external BE UT build image is refreshed through a simple required-library check instead of installed fingerprints. - Does this need documentation: No
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
hubgeter
marked this pull request as ready for review
September 2, 2026 07:33
Contributor
Author
|
run buildall |
hubgeter
marked this pull request as draft
September 2, 2026 07:40
Contributor
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
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?
Issue Number: None
Related PR: #66221, #66480
Problem Summary: The branch-4.1 Arrow 24 backport inherited an Arrow/Paimon-specific semantic-fingerprint system, installed-artifact validators, focused recovery paths, and dedicated lifecycle CI. This diverged from the standard Doris thirdparty workflow and made dependency maintenance unnecessarily complex. Follow the existing model used by other dependency upgrades: keep source versions and checksums in vars.sh, use patch markers for source preparation, rely on matching prebuilts, and use the existing platform completion sentinel for full rebuilds. The branch-4.1 BE unit-test entrypoint still supports an older install-only build image, so retain only a lightweight libarrow_compute.a check that stages and installs the shared complete prebuilt when needed.
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)