[feature](catalog) Support Alibaba Cloud OSS Tables REST catalog - #66567
Open
xylaaaaa wants to merge 2 commits into
Open
[feature](catalog) Support Alibaba Cloud OSS Tables REST catalog#66567xylaaaaa wants to merge 2 commits into
xylaaaaa wants to merge 2 commits into
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
xylaaaaa
force-pushed
the
agent/support-alibaba-oss-tables-rest-catalog
branch
from
August 7, 2026 03:28
25af2e0 to
a5fcd36
Compare
xylaaaaa
marked this pull request as ready for review
August 7, 2026 03:29
Contributor
Author
|
run buildall |
Contributor
FE UT Coverage ReportIncrement line coverage `` 🎉 |
Contributor
TPC-H: Total hot run time: 29399 ms |
Contributor
TPC-DS: Total hot run time: 159060 ms |
Contributor
ClickBench: Total hot run time: 23.94 s |
Contributor
FE Regression Coverage ReportIncrement line coverage |
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: Alibaba Cloud OSS Tables exposes an Iceberg REST Catalog that uses the osstables SigV4 service name and an S3-compatible data plane. Doris only treated Glue and S3 Tables as managed signed REST catalogs, so an OSS Tables catalog did not reuse the selected OSS credentials for REST signing and did not validate its required signing settings. Recognize osstables, reuse the same OSS credentials for the REST control plane and S3FileIO data plane, require a signing region with SigV4 enabled, and cover the official endpoint, ACS warehouse ARN, and STS token mapping.
### Release note
Support Alibaba Cloud OSS Tables through the Iceberg REST Catalog.
### Check List (For Author)
- Test: Unit Test and FE build
- ./run-fe-ut.sh --run org.apache.doris.connector.metastore.iceberg.rest.IcebergRestMetaStorePropertiesTest
- ./run-fe-ut.sh --run org.apache.doris.connector.iceberg.IcebergCatalogFactoryTest
- DISABLE_BUILD_UI=ON ./build.sh --fe
- Behavior changed: Yes. signing-name=osstables now reuses OSS/S3-compatible credentials and requires a signing region with SigV4 enabled. Managed Glue and S3 Tables catalogs also reject an explicit sigv4-enabled=false value during validation instead of failing later at runtime.
- Does this need documentation: Yes. Follow-up documentation should include the OSS Tables REST endpoint, ACS warehouse ARN, osstables signing name, and OSS S3FileIO endpoint.
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary: CREATE CATALOG connectivity validation constructed a connector context without the raw storage properties, so OSS credentials were unavailable during the validation request. At runtime, auto-detection could also bind both OSS and generic S3, and scan/write configuration merging allowed the generic S3 endpoint to overwrite the explicit OSS endpoint. Pass a snapshot of raw properties to the creation context and consistently select the cloud-specific S3-compatible binding across Iceberg catalog, scan, and write paths.
### Release note
Fix OSS Tables catalog creation and data access when OSS storage is auto-detected without fs.oss.support.
### Check List (For Author)
- Test: Unit Test and Manual test
- IcebergCatalogFactoryTest, IcebergScanPlanProviderTest, IcebergWritePlanProviderTest, and CatalogFactoryPluginRoutingTest
- Created an OSS Tables REST catalog without fs.oss.support, then created a database/table and verified INSERT and SELECT
- Behavior changed: Yes. Explicit OSS settings now take precedence over the generic S3 fallback for Iceberg catalog, scan, and write configuration.
- Does this need documentation: No
xylaaaaa
force-pushed
the
agent/support-alibaba-oss-tables-rest-catalog
branch
from
August 7, 2026 08:28
a5fcd36 to
aef2570
Compare
Contributor
Author
|
run buildall |
Contributor
TPC-H: Total hot run time: 28949 ms |
Contributor
TPC-DS: Total hot run time: 158305 ms |
Contributor
ClickBench: Total hot run time: 23.9 s |
Contributor
FE Regression Coverage ReportIncrement line coverage |
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.
What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary:
Alibaba Cloud OSS Tables exposes an Iceberg REST Catalog that uses the
osstablesSigV4 service name and an S3-compatible data plane. The plugin-driven Iceberg connector only recognized Glue and S3 Tables as managed signed REST catalogs. Consequently, an OSS Tables catalog did not reuse the selected OSS credentials for REST signing, and its required signing region and SigV4 settings were not fully validated.This change:
osstablesas a managed SigV4 signing name;sigv4-enabled=true;The current connector's connection check already initializes the real catalog through the full property-building path, so no separate connectivity-only implementation is needed.
Release note
Support Alibaba Cloud OSS Tables through the Iceberg REST Catalog.
Check List (For Author)
Test
mvn -f fe/pom.xml -pl :fe-connector-metastore-iceberg -am test -Dtest=IcebergRestMetaStorePropertiesTest -DfailIfNoTests=false(13 tests)mvn -f fe/pom.xml -pl :fe-connector-iceberg -am test -Dtest=IcebergCatalogFactoryTest -DfailIfNoTests=false(63 tests)DISABLE_BUILD_UI=ON ./build.sh --feBehavior changed:
signing-name=osstablesnow reuse OSS/S3-compatible credentials and require a signing region with SigV4 enabled. Managed Glue and S3 Tables catalogs also reject an explicitsigv4-enabled=falsevalue during validation instead of failing later at runtime.Does this need documentation?
osstablessigning name, and OSS S3FileIO endpoint.Check List (For Reviewer who merge this PR)