-
Notifications
You must be signed in to change notification settings - Fork 290
Remove extraneous trailing slash in table location #606
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
@Vitalii0-o I think it is a good idea to remove the extraneous slash, are you interested in contributing a patch? |
Of course, it’s true that I only managed to localize the problem, I don’t have a ready-made solution yet |
If you have a stack trace it would be possible to find a suitable place to trim the excess slash |
Traceback (most recent call last): app is try to find --Bucket: bucket, Key: facebook/123/bronze_facebook_test1/_dlt_pipeline_state/metadata/123.metadata.json |
This error occurred to me about a week ago, but there were no changes |
Apache Iceberg version
0.6.0 (latest release)
Please describe the bug 🐞
reating an Iceberg table from spark-3.2 with pyiceberg runtime 0.6.0 with location s3://bucket/db/tbl/ will cause underlying files be like s3://bucket/db/tbl//data/xxx. This leads to other system (e.g. Trino) file not found exception as those system will remove the duplicated slash in the string (s3://bucket/db/tbl/data/xxx).
I think the right behavior should be letting iceberg remove extraneous trailing slash in table location. i.e. when setting the table location as s3://bucket/db/tbl/. the trailing / should be removed.
In iceberg еhis issue has been solved -
apache/iceberg#4582
The text was updated successfully, but these errors were encountered: