FANNG1 opened a new pull request, #67157:
URL: https://github.com/apache/doris/pull/67157
### What problem does this PR solve?
Issue Number: close #67131
Related PR: #66805
Problem Summary:
Lance catalogs already forward provider-native storage options, but Doris
did not translate typed OSS properties and filesystem catalogs rejected
`oss://` warehouses.
This change:
- maps Doris OSS properties to Lance public OSS options;
- normalizes native Namespace-vended aliases before merging so vended values
deterministically override static values;
- rejects conflicting aliases while preserving unknown vended options;
- accepts OSS filesystem warehouses; and
- redacts OSS credentials from metadata errors.
It reuses the FE-to-BE storage-option transport introduced by #66805 and
does not change Thrift or BE code.
### Release note
Support native Alibaba Cloud OSS storage options for Lance catalogs.
### Check List (For Author)
- Test:
- Unit Test: Official Doris build image `run-fe-ut.sh`, 31 tests passed
- Manual test: PyLance real OSS write/read and Doris FE metadata access
through filesystem and REST catalogs
- Build: Full FE build and Checkstyle passed; ASAN BE compiled and
linked successfully
- Validation boundary: An end-to-end BE scan could not run because the
x86_64 ASAN binary crashes before service initialization under ARM emulation
- Behavior changed: Yes. Lance catalogs can use `oss://` with Doris OSS
properties and OSS Namespace-vended options.
- Does this need documentation: No
### Scope
Not included: role-based credential vending, STS credential refresh during a
scan, a new Thrift envelope, or static support for other object-store providers.
--
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]
