Skip to content
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

Fix inconstant iceberg default location due to final trailing slash #108

Merged
merged 3 commits into from
Nov 4, 2022

Conversation

nicor88
Copy link
Contributor

@nicor88 nicor88 commented Nov 3, 2022

Description

When working with Iceberg I noticed that the final / in the location of the table create weird extra / slash in the prefix of the objects in S3.

When using custom location of this type 's3://my_bucket/db/table' the issue doesn't persist.
Therefore I decided to use this default behaviour creating a get_iceberg_location to return default location without final /.
The final slash makes my iceberg tables unreadable from trino, somehow athena seems dealing with it, as the glue/spark.

See this related issue apache/iceberg#4582.
Using version older then 0.13 fix the issue partially, as the metadata objects still suffer of the same problem (this must be addressed to the community developing Iceberg, I will reach out), for now that is the best fix to be able to use iceberg tables with other systems.

Checklist

  • I have signed the CLA
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-glue next" section.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@menuetb menuetb merged commit 32309a9 into aws-samples:main Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants