Skip to content

branch-4.0: [refactor](oss) unify FE OSS filesystem with Jindo #61269#61416

Open
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-61269-branch-4.0
Open

branch-4.0: [refactor](oss) unify FE OSS filesystem with Jindo #61269#61416
github-actions[bot] wants to merge 1 commit intobranch-4.0from
auto-pick-61269-branch-4.0

Conversation

@github-actions
Copy link
Contributor

Cherry-picked from #61269

This PR unifies the FE-side OSS Hadoop filesystem implementation to
Jindo FS and removes legacy OSS filesystem dependencies that are no
longer needed.

## Why

We currently have multiple OSS filesystem implementations on the FE
classpath, including:
- `org.apache.hadoop.fs.aliyun.oss.AliyunOSSFileSystem`
- `paimon-oss`

This makes OSS behavior inconsistent and increases the chance of
classpath conflicts. Since Doris already packages and uses Jindo FS, FE
should consistently use Jindo instead of mixing multiple OSS filesystem
implementations.

## Changes

- Switch `OSSProperties` to use Jindo FS:
  - `fs.oss.impl = com.aliyun.jindodata.oss.JindoOssFileSystem`
  - `fs.AbstractFileSystem.oss.impl = com.aliyun.jindodata.oss.JindoOSS`
- Keep `OSSHdfsProperties` aligned with the same Jindo FS constants.
- Add FE unit test coverage to verify OSS Hadoop config is initialized
with Jindo FS.
- Remove legacy OSS filesystem dependencies from FE modules:
  - remove `paimon-oss` from `fe-core`
  - remove `paimon-oss` from `preload-extensions`
- remove `hadoop-aliyun` from FE dependency management and `hadoop-deps`

## Scope

This PR only updates FE-side OSS filesystem wiring and FE-related
dependency cleanup.
Non-FE modules are intentionally left unchanged.

## Verification

- `run-fe-ut.sh --run
org.apache.doris.datasource.property.storage.OSSPropertiesTest,org.apache.doris.datasource.property.storage.OSSHdfsPropertiesTest`
- Full FE reactor build passed

## Notes

`aliyun-sdk-oss` is still kept because it is still used by FE cloud
storage code (`OssRemote`) and is not part of the Hadoop OSS filesystem
implementation cleanup in this PR.
@github-actions github-actions bot requested a review from yiguolei as a code owner March 17, 2026 04:48
@hello-stephen
Copy link
Contributor

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 reopened this Mar 17, 2026
@hello-stephen
Copy link
Contributor

run buildall

@hello-stephen
Copy link
Contributor

FE UT Coverage Report

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

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.

3 participants