-
Notifications
You must be signed in to change notification settings - Fork 350
Closed
Description
Apache Iceberg version
0.9.1 (latest release)
Please describe the bug 🐞
When using Pyiceberg with Nessie catalog, specifying a warehouse location in the client configuration does not override the Nessie server's configured nessie.warehouse value
Pyiceberg configuration
catalog = load_catalog(
"rest",
**{
"uri": "http://localhost:19120/api/v1",
"warehouse": "s3://bucket-x",
"s3.endpoint": "http://localhost:9000",
"s3.access-key-id": "minioadmin",
"s3.secret-access-key": "minioadmin",
"s3.path-style-access": "true",
}
)
Observed behavior: Nessie's server-side warehouse path is always used and the Pyiceberg warehouse setting is ignored
Expected behavior: If a warehouse location is provided in the PyIceberg client config, it should be used for new tables.
Willingness to contribute
- I can contribute a fix for this bug independently
- I would be willing to contribute a fix for this bug with guidance from the Iceberg community
- I cannot contribute a fix for this bug at this time
Metadata
Metadata
Assignees
Labels
No labels