Skip to content

branch-4.1: [fix](paimon) add jindo oss support and token propagation #62106#62220

Merged
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62106-branch-4.1
Apr 9, 2026
Merged

branch-4.1: [fix](paimon) add jindo oss support and token propagation #62106#62220
yiguolei merged 1 commit intobranch-4.1from
auto-pick-62106-branch-4.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 8, 2026

Cherry-picked from #62106

This PR adds Jindo OSS support for Paimon and propagates OSS session
tokens into Hadoop storage config.

  Changes:
  - add `org.apache.paimon:paimon-jindo` to `fe-core`
  - add `org.apache.paimon:paimon-jindo` to `paimon-scanner`
- enable `metaInf-services` merge in `paimon-scanner` assembly packaging
so Paimon `FileIOLoader` SPI entries are preserved
- propagate `oss.session_token` to `fs.oss.securityToken` in
`OSSProperties.initializeHadoopStorageConfig`
  - add unit test coverage for OSS Hadoop config token propagation

  ## Why

  For Paimon OSS access, Doris needs Jindo FileIO on the classpath.

Also, Doris already accepts OSS session token inputs, but
`OSSProperties.initializeHadoopStorageConfig()` did not forward the
token into
Hadoop OSS config. This can break temporary-credential based OSS access.
@github-actions github-actions bot requested a review from yiguolei as a code owner April 8, 2026 07:25
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 8, 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?

@dataroaring dataroaring closed this Apr 8, 2026
@dataroaring dataroaring reopened this Apr 8, 2026
@Thearas
Copy link
Copy Markdown
Contributor

Thearas commented Apr 8, 2026

run buildall

@hello-stephen
Copy link
Copy Markdown
Contributor

FE UT Coverage Report

Increment line coverage 100.00% (2/2) 🎉
Increment coverage report
Complete coverage report

@yiguolei yiguolei merged commit 55cdace into branch-4.1 Apr 9, 2026
26 of 29 checks passed
@CalvinKirs CalvinKirs deleted the auto-pick-62106-branch-4.1 branch April 9, 2026 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants