xylaaaaa opened a new pull request, #66567:
URL: https://github.com/apache/doris/pull/66567
### 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. 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:
- recognizes `osstables` as a managed SigV4 signing name;
- reuses the selected OSS/S3-compatible AK, SK, and STS token for both the
REST control plane and S3FileIO data plane;
- requires a signing region and `sigv4-enabled=true`;
- adds coverage for the official OSS Tables endpoint shape, ACS warehouse
ARN, OSS endpoint, and session token mapping.
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 <!-- At least one of them must be included. -->
- [ ] Regression test
- [x] Unit 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` (66 tests)
- `DISABLE_BUILD_UI=ON ./build.sh --fe`
- [ ] Manual test (add detailed scripts or steps below)
- [ ] No need to test or manual test. Explain why:
- [ ] This is a refactor/code format and no logic has been changed.
- [ ] Previous test can cover this change.
- [ ] No code files have been changed.
- [ ] Other reason
- Behavior changed:
- [ ] No.
- [x] Yes. Iceberg REST catalogs with `signing-name=osstables` now reuse
OSS/S3-compatible credentials and require 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?
- [ ] No.
- [x] Yes. Follow-up documentation should include the OSS Tables REST
endpoint, ACS warehouse ARN, `osstables` signing name, and OSS S3FileIO
endpoint.
### Check List (For Reviewer who merge this PR)
- [ ] Confirm the release note
- [ ] Confirm test cases
- [ ] Confirm document
- [ ] Add branch pick label
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
