jkasprzak opened a new issue, #1757:
URL: https://github.com/apache/polaris/issues/1757
### Describe the bug
I have created a catalog with a default location and two allowed locations:
`./polaris catalogs create --storage-type s3 --default-base-location
s3://bucket1/polaris/ \
--allowed-location s3://bucket1/polaris/ --allowed-location
s3://bucket2/polaris/ \
--role-arn arn:aws:iam::<>:role/<some-role-name. quickstart_catalog`
everything works fine if I create new tables like this
```CREATE NAMESPACE IF NOT EXISTS polaris.db
CREATE TABLE polaris.db.names (
name STRING
)
USING iceberg
LOCATION 's3://bucket1/polaris/db/names'
# or just default
CREATE TABLE polaris.db.one_more_table (
name STRING
)
USING iceberg
```
but if I'm trying to use the second location
```
CREATE TABLE polaris.db.non_default (
name STRING
)
USING iceberg
LOCATION 's3://bucket2/polaris/db/non_default'
```
I'm getting this exception
`: org.apache.iceberg.exceptions.ForbiddenException: Forbidden: Invalid
locations '[s3://bucket2/polaris/db/non_default]' for identifier
'db.non_default': s3://bucket2/polaris/db/non_default is not in the list of
allowed locations: [s3://bucket1/polaris]
`
so this looks like the list of allowed locations contains only the default
one not all of them
when run `./polaris catalogs list`
I can see that both locations are in the allowedLocations
`{"type": "INTERNAL", "name": "quickstart_catalog", "properties":
{"default-base-location": "...location 1...."}, "createTimestamp":
1748582574325, "lastUpdateTimestamp": 1748582574325, "entityVersion": 1,
"storageConfigInfo": {"storageType": "S3", "allowedLocations": ["...location
1....", "...location 2...."], "roleArn": "some role"}}
`
I've tested that with Polaris 0.9 / 0.10 rc4
### To Reproduce
_No response_
### Actual Behavior
_No response_
### Expected Behavior
_No response_
### Additional context
_No response_
### System information
_No response_
--
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]
