[upgrade](thirdparty) Add aws cpp sdk kinesis #62184
[upgrade](thirdparty) Add aws cpp sdk kinesis #621840AyanamiRei wants to merge 17 commits intoapache:masterfrom
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
|
run buildall |
|
run buildall |
|
/review |
There was a problem hiding this comment.
Found 1 issue.
- [high]
be/cmake/thirdparty.cmakenow unconditionally importsaws-cpp-sdk-kinesis, but the stale-thirdparty rebuild path is still incomplete.build.shonly checks for${DORIS_THIRDPARTY}/installed/lib/hadoop_hdfs/native/libhdfs.abefore deciding whether to rerunthirdparty/build-thirdparty.sh(build.sh:354-369). On any machine or CI cache that already has thirdparty built from before this change,./build.sh --beskips rebuilding thirdparty, soinstalled/lib64/libaws-cpp-sdk-kinesis.ais still missing and the BE configure/link step fails as soon as this imported target is consumed. This PR needs to update the rebuild detection together with the new imported library.
Critical checkpoints:
- Goal of the task: Partially accomplished. The PR adds kinesis to the AWS SDK build list and BE thirdparty imports, but it does not safely handle existing thirdparty installations, so the stated goal is not met end-to-end. No build/test evidence was included to prove the upgrade path works.
- Minimality/focus: Yes. The change set is small and focused on thirdparty wiring.
- Concurrency: Not applicable.
- Special lifecycle/static init: Not applicable.
- Configuration changes: None.
- Incompatible changes: No protocol/storage compatibility concerns, but there is a build-environment compatibility regression for existing thirdparty caches.
- Parallel code paths: The relevant parallel path is the existing thirdparty reuse/rebuild flow in
build.sh; it was not updated along with the new imported library. - Special conditional checks: The existing
LAST_THIRDPARTY_LIBcheck is now too narrow for this change. - Test coverage: No regression/unit/build validation was shown. For a build-system change, at least a clean/incremental build check is needed.
- Observability: Not applicable.
- Transaction/persistence/data-write/FE-BE variable passing: Not applicable.
- Performance: No notable issue in the patch itself.
- Other issues: None beyond the incremental-build regression above.
|
run buildall |
Add function to check if thirdparty files have changed
|
run buildall |
|
run buildall |
|
run buildall |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
1 similar comment
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
used for #61325
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)