Skip to content

branch-4.0: [fix](catalog)Disable Hadoop FileSystem cache for multi-configurationobject storage catalogs #57063 #57154

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
yiguolei merged 1 commit into from
Oct 23, 2025
Merged

branch-4.0: [fix](catalog)Disable Hadoop FileSystem cache for multi-configurationobject storage catalogs #57063 #57154

yiguolei merged 1 commit into from
Oct 23, 2025

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 20, 2025

Cherry-picked from #57063

@CalvinKirs
[fix](catalog)Disable Hadoop FileSystem cache for multi-configuration…
1b603b2 
…object storage catalogs (#57063)

… 

Iceberg and Paimon catalogs access object storage (OSS, OBS, etc.) using
Hadoop FileSystem libraries. In environments with multiple storage
configurations, the FileSystem cache may cause instances to be shared
across configurations, leading to potential conflicts or incorrect
access.

This PR disables the Hadoop FileSystem cache
(`fs.oss.impl.disable.cache=true`) for each OSS to ensure configuration
isolation and prevent cache overwrites.

If necessary, the cache can also be explicitly enabled for specific
catalogs
by setting `fs.oss.impl.disable.cache=false`.
@github-actions github-actions bot requested a review from yiguolei as a code owner October 20, 2025 07:46
@hello-stephen
Copy link
Contributor

hello-stephen commented Oct 20, 2025

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 Oct 20, 2025
@hello-stephen
Copy link
Contributor

hello-stephen commented Oct 20, 2025

run buildall

@yiguolei yiguolei merged commit 5492afb into branch-4.0 Oct 23, 2025
25 of 27 checks passed
@github-actions github-actions bot deleted the auto-pick-57063-branch-4.0 branch October 23, 2025 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@hello-stephen @yiguolei @dataroaring @CalvinKirs