[Bug] Doris does not support accessing Iceberg external tables based on BOS.
- Dominant language
- Java
- Stars
- 15.9k
- Forks
- 3.9k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 520
Description
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues.
### Version
Doris 4.1
### What's Wrong?
When Iceberg data is stored on BOS, creating a corresponding Iceberg catalog in Doris and then querying data from or inserting data into the tables will both result in errors.
### What You Expected?
The SELECT and INSERT SQL statements can be executed successfully.
### How to Reproduce?
1. prepare Iceberg data stored on BOS
2. create iceberg catalog like this:
CREATE CATALOG `catalog_name` PROPERTIES (
"warehouse" = "bos://icebergdata/warehouse/",
"type" = "iceberg",
"s3.secret_key" = "your_sk",
"s3.region" = "bj",
"s3.endpoint" = "your_endpoint",
"s3.access_key" = "your_ak",
"iceberg.catalog.type" = "hadoop",
"fs.bos.impl" = "org.apache.hadoop.fs.s3a.S3AFileSystem"
);
3. try insert & select
### Anything Else?
_No response_
### Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
Start by reproducing the issue with Iceberg data on BOS and the catalog properties shown in the report. Try both the SELECT and INSERT statements, recording the resulting errors and comparing the BOS configuration with a working Iceberg catalog. Done means both statements execute successfully against the external tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hadoop, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100