You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@polaris.apache.org by "jkasprzak (via GitHub)" <gi...@apache.org> on 2025/05/30 05:42:15 UTC
[I] Cannot create tables for allowed location [polaris]
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: issues-unsubscribe@polaris.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Cannot create tables for allowed location different than default [polaris]
Posted by "jkasprzak (via GitHub)" <gi...@apache.org>.
jkasprzak commented on issue #1757:
URL: https://github.com/apache/polaris/issues/1757#issuecomment-2933647994
no, I'm using the same namespace and schema for all three tables:
- the first one - `polaris.db.names` has been created sucessfully in the location that overlaps the default one for the catalog (explicit location : `LOCATION 's3://bucket1/polaris/db/names'`
- the second - `polaris.db.one_more_table ` has been created sucessfully in the default location for the catalog `--default-base-location s3://bucket1/polaris/`
- the last one - `polaris.db.non_default` uses a custom location that has been registered as `allowed-locations` and this fails... and as you see the error says that the location is not in the list of allowed locations..... (and here you see the default one for this catalog)
--
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Cannot create tables for allowed location different than default [polaris]
Posted by "eric-maynard (via GitHub)" <gi...@apache.org>.
eric-maynard commented on issue #1757:
URL: https://github.com/apache/polaris/issues/1757#issuecomment-2940458221
That's the issue @jkasprzak , you're trying to create a table that resides outside of its parent namespace. To do that, you'd need to set `ALLOW_UNSTRUCTURED_TABLE_LOCATION`.
--
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Cannot create tables for allowed location different than default [polaris]
Posted by "eric-maynard (via GitHub)" <gi...@apache.org>.
eric-maynard closed issue #1757: Cannot create tables for allowed location different than default
URL: https://github.com/apache/polaris/issues/1757
--
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Cannot create tables for allowed location different than default [polaris]
Posted by "eric-maynard (via GitHub)" <gi...@apache.org>.
eric-maynard commented on issue #1757:
URL: https://github.com/apache/polaris/issues/1757#issuecomment-2922875948
It looks like the table resides outside the location of the namespace -- can you confirm?
--
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: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org