Skip to content

[upgrade](thirdparty) Add aws cpp sdk kinesis #62184

Open
0AyanamiRei wants to merge 17 commits intoapache:masterfrom
0AyanamiRei:up-thirdparty-aws-kinesis
Open

[upgrade](thirdparty) Add aws cpp sdk kinesis #62184
0AyanamiRei wants to merge 17 commits intoapache:masterfrom
0AyanamiRei:up-thirdparty-aws-kinesis

Conversation

@0AyanamiRei
Copy link
Copy Markdown
Contributor

@0AyanamiRei 0AyanamiRei commented Apr 7, 2026

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

    • Regression test
    • Unit Test
    • Manual test (add detailed scripts or steps below)
    • No need to test or manual test. Explain why:
      • This is a refactor/code format and no logic has been changed.
      • Previous test can cover this change.
      • No code files have been changed.
      • Other reason
  • Behavior changed:

    • No.
    • Yes.
  • Does this need documentation?

    • No.
    • Yes.

Check List (For Reviewer who merge this PR)

  • Confirm the release note
  • Confirm test cases
  • Confirm document
  • Add branch pick label

@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 7, 2026

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

liaoxin01
liaoxin01 previously approved these changes Apr 8, 2026
Copy link
Copy Markdown
Contributor

@liaoxin01 liaoxin01 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Apr 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 8, 2026

PR approved by anyone and no changes requested.

Copy link
Copy Markdown
Contributor

@sollhui sollhui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@morningman
Copy link
Copy Markdown
Contributor

run buildall

@0AyanamiRei
Copy link
Copy Markdown
Contributor Author

run buildall

@github-actions github-actions bot removed the approved Indicates a PR has been approved by one committer. label Apr 8, 2026
@0AyanamiRei
Copy link
Copy Markdown
Contributor Author

run buildall

@0AyanamiRei
Copy link
Copy Markdown
Contributor Author

/review

Copy link
Copy Markdown
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found 1 issue.

  1. [high] be/cmake/thirdparty.cmake now unconditionally imports aws-cpp-sdk-kinesis, but the stale-thirdparty rebuild path is still incomplete. build.sh only checks for ${DORIS_THIRDPARTY}/installed/lib/hadoop_hdfs/native/libhdfs.a before deciding whether to rerun thirdparty/build-thirdparty.sh (build.sh:354-369). On any machine or CI cache that already has thirdparty built from before this change, ./build.sh --be skips rebuilding thirdparty, so installed/lib64/libaws-cpp-sdk-kinesis.a is 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_LIB check 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.

Comment thread be/cmake/thirdparty.cmake
@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

Add function to check if thirdparty files have changed
@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@0AyanamiRei
Copy link
Copy Markdown
Contributor Author

run buildall

@0AyanamiRei
Copy link
Copy Markdown
Contributor Author

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

BE UT Coverage Report

Increment line coverage 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 53.09% (20178/38008)
Line Coverage 36.66% (190004/518251)
Region Coverage 32.90% (147468/448172)
Branch Coverage 34.04% (64572/189674)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.65% (23684/37208)
Line Coverage 47.17% (243605/516488)
Region Coverage 44.18% (199771/452206)
Branch Coverage 45.38% (86317/190194)

@sollhui
Copy link
Copy Markdown
Contributor

sollhui commented Apr 17, 2026

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.40% (23642/37288)
Line Coverage 46.84% (242637/518027)
Region Coverage 43.94% (199081/453069)
Branch Coverage 45.07% (85908/190591)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.27% (23597/37297)
Line Coverage 46.77% (242325/518153)
Region Coverage 43.89% (198912/453176)
Branch Coverage 45.04% (85870/190635)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.24% (23586/37297)
Line Coverage 46.81% (242536/518153)
Region Coverage 43.92% (199051/453176)
Branch Coverage 45.10% (85982/190635)

1 similar comment
@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.24% (23586/37297)
Line Coverage 46.81% (242536/518153)
Region Coverage 43.92% (199051/453176)
Branch Coverage 45.10% (85982/190635)

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.50% (23683/37295)
Line Coverage 46.99% (243452/518142)
Region Coverage 44.08% (199763/453174)
Branch Coverage 45.25% (86265/190635)

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

BE Regression && UT Coverage Report

Increment line coverage 100% (0/0) 🎉

Increment coverage report
Complete coverage report

Category Coverage
Function Coverage 63.35% (23635/37309)
Line Coverage 46.86% (242890/518344)
Region Coverage 43.88% (198978/453460)
Branch Coverage 45.10% (85991/190678)

@hello-stephen
Copy link
Copy Markdown
Contributor

run buildall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants