[feat](Iceberg)Rest & S3Table Support Iam-role by CalvinKirs · Pull Request #60498 · apache/doris

CalvinKirs · 2026-02-04T09:53:47Z

FYI #59893

The initial implementation was contributed by https://github.com/Sbaia . Many thanks for his contributions.

hello-stephen · 2026-02-04T09:53:59Z

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:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?
Which functions were optimized and what is the difference before and after the optimization?

CalvinKirs · 2026-02-04T09:54:19Z

run buildall

hello-stephen · 2026-02-04T11:01:44Z

FE UT Coverage Report

Increment line coverage 69.39% (34/49) 🎉
Increment coverage report
Complete coverage report

doris-robot · 2026-02-04T11:09:08Z

TPC-H: Total hot run time: 31840 ms

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools
Tpch sf100 test result on commit e3ae91676c5ddb5f65020c808185ce5b0f76cee1, data reload: false
------ Round 1 ----------------------------------
q1	17616	5306	5074	5074
q2	1993	306	210	210
q3	10226	1287	756	756
q4	10214	873	316	316
q5	7560	2191	1914	1914
q6	203	194	150	150
q7	883	741	607	607
q8	9276	1400	1089	1089
q9	5356	4843	4898	4843
q10	6841	1942	1573	1573
q11	493	303	287	287
q12	382	382	234	234
q13	17768	4096	3234	3234
q14	248	241	219	219
q15	938	833	811	811
q16	698	671	615	615
q17	649	864	424	424
q18	6737	6488	6403	6403
q19	1291	1140	652	652
q20	404	350	240	240
q21	2631	2124	1912	1912
q22	360	322	277	277
Total cold run time: 102767 ms
Total hot run time: 31840 ms
----- Round 2, with runtime_filter_mode=off -----
q1	5351	5293	5261	5261
q2	277	332	250	250
q3	2149	2732	2272	2272
q4	1361	1734	1301	1301
q5	4286	4160	4226	4160
q6	225	181	137	137
q7	2335	2080	1847	1847
q8	2592	2551	2409	2409
q9	7463	7381	7613	7381
q10	2884	3064	2681	2681
q11	551	488	442	442
q12	680	761	620	620
q13	3938	4544	3609	3609
q14	299	341	286	286
q15	882	821	825	821
q16	692	714	656	656
q17	1205	1312	1335	1312
q18	8007	7818	7906	7818
q19	905	878	880	878
q20	2122	2237	2018	2018
q21	4720	4160	4081	4081
q22	563	546	494	494
Total cold run time: 53487 ms
Total hot run time: 50734 ms

doris-robot · 2026-02-04T11:25:44Z

ClickBench: Total hot run time: 28.31 s

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/clickbench-tools
ClickBench test result on commit e3ae91676c5ddb5f65020c808185ce5b0f76cee1, data reload: false
query1	0.05	0.04	0.05
query2	0.09	0.05	0.05
query3	0.25	0.08	0.09
query4	1.61	0.11	0.11
query5	0.27	0.25	0.24
query6	1.16	0.66	0.67
query7	0.03	0.02	0.03
query8	0.05	0.04	0.05
query9	0.55	0.50	0.48
query10	0.55	0.55	0.54
query11	0.13	0.10	0.10
query12	0.14	0.10	0.11
query13	0.64	0.61	0.62
query14	1.07	1.06	1.05
query15	0.87	0.85	0.87
query16	0.40	0.39	0.40
query17	1.14	1.14	1.14
query18	0.23	0.22	0.21
query19	2.01	1.93	1.96
query20	0.02	0.01	0.01
query21	15.40	0.26	0.15
query22	4.95	0.06	0.05
query23	15.81	0.30	0.12
query24	1.10	0.67	0.34
query25	0.08	0.12	0.07
query26	0.15	0.14	0.14
query27	0.06	0.06	0.06
query28	3.82	1.16	0.97
query29	12.58	3.95	3.18
query30	0.29	0.13	0.12
query31	2.82	0.64	0.40
query32	3.23	0.60	0.49
query33	3.28	3.27	3.21
query34	16.05	5.37	4.77
query35	4.81	4.84	4.75
query36	0.65	0.50	0.48
query37	0.11	0.07	0.06
query38	0.07	0.05	0.04
query39	0.04	0.03	0.03
query40	0.20	0.16	0.14
query41	0.08	0.04	0.03
query42	0.04	0.02	0.02
query43	0.05	0.04	0.04
Total cold run time: 96.93 s
Total hot run time: 28.31 s

hello-stephen · 2026-02-04T14:02:48Z

FE Regression Coverage Report

Increment line coverage 0.00% (0/49) 🎉
Increment coverage report
Complete coverage report

Sbaia · 2026-02-05T08:09:03Z

Thanks for picking this up and building on #59893, @CalvinKirs.

I want to clarify an important distinction about what this PR actually enables vs. what users on EKS/GKE typically need.

What this PR adds: cross-account assume-role support (AssumeRoleAwsClientFactory), where a role_arn is explicitly provided in the catalog properties.

What this PR does NOT add: support for IRSA (IAM Roles for Service Accounts) or, more generally, the AWS default credentials chain without any explicit credential configuration.

The validation in IcebergRestProperties (lines 128-137) explicitly rejects the case where neither access-key/secret-key nor role_arn is provided:

booleanhasAccessKeyAndSecret = ...;
booleanhasIamRole = ...;
return !hasAccessKeyAndSecret && !hasIamRole; // fails validation

With IRSA (and future equivalents like GKE Workload Identity or ECS task roles), the pod already has credentials injected via the service account. The user doesn't have a role_arn to specify in the catalog DDL — the role is attached to the pod's ServiceAccount via the eks.amazonaws.com/role-arn annotation. The correct behavior is to let Iceberg use the AWS SDK's DefaultCredentialsProvider, which picks up the IRSA token automatically. This means accepting a catalog definition with no credential properties at all.

Regarding the assume-role path itself:AssumeRoleAwsClientFactory uses the AWS SDK's default credentials chain internally to obtain the base credentials needed to call sts:AssumeRole. So who actually performs the AssumeRole call depends on the environment:

EKS with IRSA configured: the pod's ServiceAccount role (via web identity token) is used as the base identity to assume the target role. This requires a trust policy on the target role that allows the SA role to assume it.
EKS without IRSA: falls back to the EC2 instance profile (node role via IMDS). The node role needs sts:AssumeRole permission on the target role. This is less secure since all pods on the node share the same base identity.
EC2 (non-Kubernetes): the instance profile role is used directly.

So the assume-role feature works, but it's solving a different use case (cross-account access) than what most EKS users need (direct IRSA credentials without specifying any role_arn).

Our original PR #59893 takes a simpler approach: when no explicit credentials are provided, we just don't set any credential properties, allowing Iceberg/AWS SDK to resolve credentials through the default chain. This covers IRSA, instance profiles, environment variables, and any future pod identity mechanism — with zero configuration in the catalog DDL.

I'd suggest either:

Relaxing the validation to allow no credentials at all (supporting both IRSA and assume-role), or
Keeping assume-role as an addition on top of [Enhancement](iceberg) Support AWS default credentials chain for S3 Tables and REST catalogs #59893's default-chain support

Happy to collaborate on merging the two approaches.

CalvinKirs · 2026-02-09T03:54:49Z

Thanks for picking this up and building on #59893, @CalvinKirs.↳
I want to clarify an important distinction about what this PR actually enables vs. what users on EKS/GKE typically need.
What this PR adds: cross-account assume-role support (AssumeRoleAwsClientFactory), where a role_arn is explicitly provided in the catalog properties.↳
What this PR does NOT add: support for IRSA (IAM Roles for Service Accounts) or, more generally, the AWS default credentials chain without any explicit credential configuration.↳
The validation in IcebergRestProperties (lines 128-137) explicitly rejects the case where neither access-key/secret-key nor role_arn is provided:↳
booleanhasAccessKeyAndSecret = ...;
booleanhasIamRole = ...;
return !hasAccessKeyAndSecret && !hasIamRole; // fails validation
With IRSA (and future equivalents like GKE Workload Identity or ECS task roles), the pod already has credentials injected via the service account. The user doesn't have a role_arn to specify in the catalog DDL — the role is attached to the pod's ServiceAccount via the eks.amazonaws.com/role-arn annotation. The correct behavior is to let Iceberg use the AWS SDK's DefaultCredentialsProvider, which picks up the IRSA token automatically. This means accepting a catalog definition with no credential properties at all.↳
Regarding the assume-role path itself:AssumeRoleAwsClientFactory uses the AWS SDK's default credentials chain internally to obtain the base credentials needed to call sts:AssumeRole. So who actually performs the AssumeRole call depends on the environment:↳
EKS with IRSA configured: the pod's ServiceAccount role (via web identity token) is used as the base identity to assume the target role. This requires a trust policy on the target role that allows the SA role to assume it.
EKS without IRSA: falls back to the EC2 instance profile (node role via IMDS). The node role needs sts:AssumeRole permission on the target role. This is less secure since all pods on the node share the same base identity.
EC2 (non-Kubernetes): the instance profile role is used directly.
So the assume-role feature works, but it's solving a different use case (cross-account access) than what most EKS users need (direct IRSA credentials without specifying any role_arn).↳
Our original PR #59893 takes a simpler approach: when no explicit credentials are provided, we just don't set any credential properties, allowing Iceberg/AWS SDK to resolve credentials through the default chain. This covers IRSA, instance profiles, environment variables, and any future pod identity mechanism — with zero configuration in the catalog DDL.
I'd suggest either:
Relaxing the validation to allow no credentials at all (supporting both IRSA and assume-role), or
Keeping assume-role as an addition on top of [Enhancement Support AWS default credentials chain for S3 Tables and REST catalogs [Enhancement](iceberg) Support AWS default credentials chain for S3 Tables and REST catalogs #59893]([Enhancement](iceberg) Support AWS default credentials chain for S3 Tables and REST catalogs #59893 default-chain support
Happy to collaborate on merging the two approaches.

@Sbaia Hi, It turns out I can set client.impl by making a small tweak to the default. Would you mind giving it another try to see if that works for you?

CalvinKirs · 2026-02-09T03:54:57Z

run buildall

doris-robot · 2026-02-09T04:44:28Z

TPC-H: Total hot run time: 30129 ms

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/tpch-tools
Tpch sf100 test result on commit eaf74d278731e58d94a27de1679c2d3e5ec7bd34, data reload: false
------ Round 1 ----------------------------------
q1	17615	4468	4276	4276
q2	2035	344	234	234
q3	10173	1274	697	697
q4	10197	771	306	306
q5	7506	2169	1941	1941
q6	199	183	149	149
q7	896	734	618	618
q8	9263	1573	1065	1065
q9	4718	4593	4580	4580
q10	6826	1952	1544	1544
q11	514	298	265	265
q12	345	375	222	222
q13	17775	4061	3217	3217
q14	227	231	210	210
q15	892	797	798	797
q16	688	677	617	617
q17	671	745	599	599
q18	6999	5786	5753	5753
q19	1089	983	630	630
q20	493	480	386	386
q21	2495	1816	1746	1746
q22	343	308	277	277
Total cold run time: 101959 ms
Total hot run time: 30129 ms
----- Round 2, with runtime_filter_mode=off -----
q1	4335	4369	4333	4333
q2	253	323	256	256
q3	2078	2673	2234	2234
q4	1342	1742	1306	1306
q5	4241	4156	4153	4153
q6	216	181	136	136
q7	1803	1773	1681	1681
q8	2458	2633	2521	2521
q9	7785	7524	7453	7453
q10	2817	3119	2640	2640
q11	543	504	445	445
q12	709	761	618	618
q13	4012	4293	3535	3535
q14	319	401	324	324
q15	932	843	810	810
q16	742	703	670	670
q17	1119	1293	1346	1293
q18	8520	7883	7993	7883
q19	903	873	869	869
q20	2068	2159	1885	1885
q21	4479	4214	4138	4138
q22	579	533	518	518
Total cold run time: 52253 ms
Total hot run time: 49701 ms

doris-robot · 2026-02-09T05:01:18Z

ClickBench: Total hot run time: 28.15 s

machine: 'aliyun_ecs.c7a.8xlarge_32C64G'
scripts: https://github.com/apache/doris/tree/master/tools/clickbench-tools
ClickBench test result on commit eaf74d278731e58d94a27de1679c2d3e5ec7bd34, data reload: false
query1	0.06	0.06	0.05
query2	0.10	0.04	0.04
query3	0.25	0.08	0.09
query4	1.60	0.11	0.11
query5	0.28	0.28	0.24
query6	1.18	0.67	0.68
query7	0.03	0.03	0.03
query8	0.05	0.04	0.04
query9	0.58	0.49	0.49
query10	0.55	0.54	0.55
query11	0.14	0.10	0.10
query12	0.13	0.10	0.10
query13	0.64	0.61	0.62
query14	1.05	1.06	1.07
query15	0.88	0.86	0.86
query16	0.39	0.38	0.41
query17	1.07	1.11	1.15
query18	0.23	0.21	0.22
query19	2.04	1.99	2.00
query20	0.02	0.02	0.02
query21	15.45	0.26	0.15
query22	5.02	0.07	0.06
query23	15.67	0.29	0.11
query24	1.80	0.98	0.23
query25	0.10	0.08	0.07
query26	0.15	0.13	0.14
query27	0.06	0.04	0.06
query28	4.82	1.13	0.96
query29	12.59	3.84	3.15
query30	0.29	0.13	0.11
query31	2.82	0.63	0.41
query32	3.23	0.62	0.49
query33	3.22	3.22	3.26
query34	16.48	5.38	4.73
query35	4.76	4.71	4.79
query36	0.66	0.50	0.48
query37	0.11	0.07	0.08
query38	0.08	0.04	0.04
query39	0.05	0.03	0.03
query40	0.20	0.15	0.14
query41	0.10	0.03	0.03
query42	0.04	0.03	0.02
query43	0.04	0.05	0.04
Total cold run time: 99.01 s
Total hot run time: 28.15 s

hello-stephen · 2026-02-09T05:13:36Z

FE UT Coverage Report

Increment line coverage 65.67% (44/67) 🎉
Increment coverage report
Complete coverage report

hello-stephen · 2026-02-09T07:28:57Z

FE Regression Coverage Report

Increment line coverage 0.00% (0/67) 🎉
Increment coverage report
Complete coverage report

CalvinKirs · 2026-02-24T02:09:08Z

@Sbaia Hi, Could you take a look

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Fix a rebase conflict residue in Iceberg REST custom signing-name test so explicit credentials are provided when credential properties are expected. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Deduplicate Iceberg REST and S3Tables AWS credential property priority handling while keeping their explicit credential key formats separate. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Use a Doris Iceberg AWS assume-role credentials provider so REST, S3Tables, and S3 FileIO assume-role credentials honor the configured AWS credentials provider type as the STS source provider. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Pass standard Iceberg assume-role and source credentials-provider properties into the Doris Iceberg assume-role provider so the provider does not reparse Doris credentials_provider_type. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Build Iceberg assume-role provider properties from Doris S3Properties and pass only the resolved primitive values into the Iceberg credentials provider. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Reuse Doris S3Properties as the source for Iceberg assume-role credentials provider configuration and pass S3Properties-compatible provider parameters through Iceberg/S3Tables SPI. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Share Iceberg REST and S3Tables AWS credential property construction, avoid provider-specific S3 parameters for standard AWS providers, and build S3Tables control-plane and S3 FileIO clients from S3Properties for explicit credentials and IAM role support. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Remove the Doris-specific Iceberg S3 FileIO client factory and pass standard Iceberg assume-role properties directly. Explicit AK/SK and non-role credential provider modes continue to use Iceberg/AWS SDK standard properties. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Move S3 FileIO credential property construction and S3Tables runtime AWS credentials provider selection into the shared Iceberg AWS credential helper, keeping S3Tables-specific client construction local. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest,org.apache.doris.datasource.property.metastore.IcebergS3TablesMetaStorePropertiesTest - Behavior changed: No - Does this need documentation: No

CalvinKirs · 2026-04-27T09:27:29Z

run buildall

hello-stephen · 2026-04-27T11:49:21Z

FE Regression Coverage Report

Increment line coverage 0.81% (1/124) 🎉
Increment coverage report
Complete coverage report

### What problem does this PR solve? Issue Number: None Related PR: None Problem Summary: Iceberg REST catalog exposed iceberg.rest.role_arn, but REST SigV4 signing does not support this Doris property without an explicit credentials provider wrapper. Reject the unsupported property and keep REST signing on AK/SK or credentials_provider_type. ### Release note None ### Check List (For Author) - Test: Unit Test - ./run-fe-ut.sh --run org.apache.doris.datasource.property.metastore.IcebergRestPropertiesTest - Behavior changed: Yes. Iceberg REST catalog now rejects unsupported iceberg.rest.role_arn instead of mapping it to Iceberg assume-role client factory properties. - Does this need documentation: No

github-actions · 2026-05-07T03:01:41Z

PR approved by anyone and no changes requested.

FYI apache#59893 The initial implementation was contributed by https://github.com/Sbaia . Many thanks for his contributions.

…63655) #60498

) (#63848) ### What problem does this PR solve? Issue Number: None Related PR: #60498

FYI apache#59893 The initial implementation was contributed by https://github.com/Sbaia . Many thanks for his contributions.

…lugin The iceberg system tables ($snapshots, $files, ...) are the one part of iceberg BE reads through Java: FE plans the scan and Java-serializes each FileScanTask across, and only iceberg's own library can turn one back into rows. That makes this module a plugin like any other - its own directory, its own classloader, its own copy of everything it needs. What it needs turns out to be less than the shared preload layer was handing it. A plugin only ever deserializes a task and the FileIO inside it; it never builds a catalog, so the AWS catalog clients (glue, dynamodb, s3tables) stay in FE and the plugin carries only the FileIO half of the SDK. kms stays despite nothing here encrypting anything: AwsClientFactories resolves a kms class in its static initializer, so without it the S3 path dies before it starts. Hadoop, by contrast, has to be added - it used to arrive from lib/hadoop_hdfs on BE's system classpath, which a plugin cannot see. Logging needed one bridge rather than three. Dropping hadoop's reload4j - a second logging implementation, and reachable only from a servlet and a daemon banner - also takes commons-logging's discovery down to its JDK14 backend, so httpclient's output on the S3 path lands in jni.log by itself. Only fe-kerberos, which speaks log4j2, needs a bridge. CustomAwsCredentialsProvider goes. It was reached by class name from a catalog property FE no longer emits: its fe-core twin was deleted with apache#60498, which moved the s3tables catalog to a hand-built client, and FE now names only the AWS SDK's own providers there. Nothing in FE, BE, or the regression suites mentions it. The scanner keeps its factory named sys-table rather than the reader every other connector publishes, because it is not iceberg's reader: data files go through BE's native readers, and this serves the metadata tables alone.

CalvinKirs added 4 commits April 25, 2026 08:32

[feat](Iceberg)Rest & S3Table Support Iam-role
da58f00

[feat](Iceberg)Rest & S3Table Support Iam-role
726d1ce

[feat](Iceberg)Rest & S3Table Support Iam-role
7eaa2ea

CalvinKirs force-pushed the master-rest-iceberg-iam-role branch from eaf74d2 to 71a2372Compare April 27, 2026 02:34

CalvinKirs added 8 commits April 27, 2026 10:50

github-actionsBot added approved Indicates a PR has been approved by one committer. reviewed labels May 7, 2026

CalvinKirs merged commit ceeb9bc into apache:masterMay 7, 2026
30 of 31 checks passed

github-actionsBot added dev/4.0.x-conflict dev/4.1.x-conflict labels May 7, 2026

CalvinKirs deleted the master-rest-iceberg-iam-role branch May 19, 2026 11:25

CalvinKirs mentioned this pull request May 26, 2026
branch-4.1: [feat](Iceberg)Rest & S3Table Support Iam-role (#60498) #63655
Merged

yiguolei pushed a commit that referenced this pull request May 28, 2026
branch-4.1: [feat](Iceberg)Rest & S3Table Support Iam-role (#60498) (#…
dee2264
…63655) #60498

CalvinKirs mentioned this pull request May 28, 2026
branch-4.0: [feature](iceberg) Support REST and S3Table IAM role (#60498) #63848
Merged

morningman pushed a commit that referenced this pull request May 29, 2026
branch-4.0: [feature](iceberg) Support REST and S3Table IAM role (#60498
f0f47d6
) (#63848) ### What problem does this PR solve? Issue Number: None Related PR: #60498

morningman added dev/4.0.6-merged and removed dev/4.0.x dev/4.0.x-conflict labels May 29, 2026

CalvinKirs added dev/4.1.2-merged and removed dev/4.1.x dev/4.1.x-conflict labels May 29, 2026

morningman mentioned this pull request Jun 3, 2026
4.0.6 Release Notes #64065
Closed

zhaorongsheng pushed a commit to zhaorongsheng/doris that referenced this pull request Jun 4, 2026
[feat](Iceberg)Rest & S3Table Support Iam-role (apache#60498)
b438f9c
FYI apache#59893 The initial implementation was contributed by https://github.com/Sbaia . Many thanks for his contributions.

yiguolei mentioned this pull request Jun 14, 2026
4.1.2 Release Notes #64485
Closed

morningman mentioned this pull request Jul 3, 2026
[Discuss] Doris Roadmap 2026 #60036
Open
76 tasks

Uh oh!

Conversation

CalvinKirs commented Feb 4, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hello-stephen commented Feb 4, 2026

Uh oh!

CalvinKirs commented Feb 4, 2026

Uh oh!

hello-stephen commented Feb 4, 2026

FE UT Coverage Report

Uh oh!

doris-robot commented Feb 4, 2026

Uh oh!

doris-robot commented Feb 4, 2026

Uh oh!

hello-stephen commented Feb 4, 2026

FE Regression Coverage Report

Uh oh!

Sbaia commented Feb 5, 2026

Uh oh!

CalvinKirs commented Feb 9, 2026

Uh oh!

CalvinKirs commented Feb 9, 2026

Uh oh!

doris-robot commented Feb 9, 2026

Uh oh!

doris-robot commented Feb 9, 2026

Uh oh!

hello-stephen commented Feb 9, 2026

FE UT Coverage Report

Uh oh!

hello-stephen commented Feb 9, 2026

FE Regression Coverage Report

Uh oh!

CalvinKirs commented Feb 24, 2026

Uh oh!

CalvinKirs commented Apr 27, 2026

Uh oh!

hello-stephen commented Apr 27, 2026

FE Regression Coverage Report

Uh oh!

github-actionsBot commented May 7, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

CalvinKirs commented Feb 4, 2026•
edited
Loading