-
Notifications
You must be signed in to change notification settings - Fork 238
Unable to use AWS S3 locations with quotes in path #1545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is odd - without adding an external ID, this works as expected. But not when adding the external ID...
yields the following logs:
But:
yields:
Seems from the exception that this is coming back from Iceberg? Let me investigate further. EDIT: I saw this originally because there were no other catalogs in my DB when I was starting - will post in the next message, this exception happens when we are parsing current catalog locations. This issue is indeed replicable, just not with only the steps provided. One must add 2 catalogs with locations that have the quote character: the first call will succeed, the second will fail - given that you are starting with no catalogs that already have the quote character. |
The line of code that is causing this bug is that we are attempting to convert all existing existing catalogs' locations to Java URIs while checking if this new catalog location is a child of any other catalogs: polaris/polaris-core/src/main/java/org/apache/polaris/core/storage/StorageLocation.java Line 48 in 9e6226a
Will research tomorrow if there's an easy way to modify this line to not use URIs. |
Opened a fix - #1586. :) |
Describe the bug
Polaris fails to accept S3 locations that are valid in AWS, but contain
"
in the path.For example:
s3://example/pol"3/
To Reproduce
Actual Behavior
Expected Behavior
No exception
Additional context
The example location is considered valid in AWS UI. It is possible to create it and copy its S3 location in AWS UI.
System information
Local Polaris Server build as of commit 04c4f91
The text was updated successfully, but these errors were encountered: