[fix](iceberg) Support client.region and iceberg.rest.* properties invended credentials#57521
Merged
zy-kkk merged 1 commit intoapache:masterfrom Oct 31, 2025
Merged
Conversation
… vended credentials
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Member
Author
|
run buildall |
ClickBench: Total hot run time: 27.9 s |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
FE Regression Coverage ReportIncrement line coverage |
CalvinKirs
approved these changes
Oct 31, 2025
github-actions bot
pushed a commit
that referenced
this pull request
Oct 31, 2025
…vended credentials (#57521) When using Iceberg REST catalog with vended credentials enabled: - **Polaris** returns `s3.region`, `s3.access-key-id`, etc. - **Gravitino** returns `client.region`, `s3.access-key-id`, etc. (following Iceberg official naming) Current implementation only filters properties with `s3.`, `oss.`, etc. prefixes, causing `client.region` to be filtered out, which leads to `No storage properties found for schema: s3` error.
github-actions bot
pushed a commit
that referenced
this pull request
Oct 31, 2025
…vended credentials (#57521) When using Iceberg REST catalog with vended credentials enabled: - **Polaris** returns `s3.region`, `s3.access-key-id`, etc. - **Gravitino** returns `client.region`, `s3.access-key-id`, etc. (following Iceberg official naming) Current implementation only filters properties with `s3.`, `oss.`, etc. prefixes, causing `client.region` to be filtered out, which leads to `No storage properties found for schema: s3` error.
dwdwqfwe
pushed a commit
to dwdwqfwe/doris
that referenced
this pull request
Oct 31, 2025
…vended credentials (apache#57521) When using Iceberg REST catalog with vended credentials enabled: - **Polaris** returns `s3.region`, `s3.access-key-id`, etc. - **Gravitino** returns `client.region`, `s3.access-key-id`, etc. (following Iceberg official naming) Current implementation only filters properties with `s3.`, `oss.`, etc. prefixes, causing `client.region` to be filtered out, which leads to `No storage properties found for schema: s3` error.
yiguolei
pushed a commit
that referenced
this pull request
Nov 5, 2025
…vended credentials (#57521) When using Iceberg REST catalog with vended credentials enabled: - **Polaris** returns `s3.region`, `s3.access-key-id`, etc. - **Gravitino** returns `client.region`, `s3.access-key-id`, etc. (following Iceberg official naming) Current implementation only filters properties with `s3.`, `oss.`, etc. prefixes, causing `client.region` to be filtered out, which leads to `No storage properties found for schema: s3` error.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using Iceberg REST catalog with vended credentials enabled:
s3.region,s3.access-key-id, etc.client.region,s3.access-key-id, etc. (following Iceberg official naming)Current implementation only filters properties with
s3.,oss., etc. prefixes, causingclient.regionto be filtered out, which leads toNo storage properties found for schema: s3error.