Skip to content
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.

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

Correctly cache S3 client in S3 native FS with security mapping #23710

Merged
merged 1 commit into from
Oct 9, 2024

Conversation

nineinchnick
Copy link
Member

Description

S3 native FS with security mapping enabled is supposed to cache S3 clients for mappings resolved using both an identity and location. This change avoids creating new caches when resolving locations.

Fixes #23545

Additional context and related issues

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

S3 native FS with security mapping enabled is supposed to cache S3
clients for mappings resolved using both an identity and location.
This change avoids creating new caches when resolving locations.
@wendigo wendigo merged commit 8916dce into trinodb:master Oct 9, 2024
121 of 127 checks passed
@github-actions github-actions bot added this to the 461 milestone Oct 9, 2024
@nineinchnick nineinchnick deleted the s3-secmap-cache branch October 10, 2024 08:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Unable to load credentials from any of the providers in the chain file with native s3 support
4 participants