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.

Sign up for GitHub

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

Jump to bottom

Data loss due to lack of commit orchestration in Iceberg #9583

Closed
findepi opened this issue Oct 11, 2021 · 0 comments · Fixed by #9584
Closed

Data loss due to lack of commit orchestration in Iceberg #9583

findepi opened this issue Oct 11, 2021 · 0 comments · Fixed by #9584
Labels
bug Something isn't working correctness
Milestone
364

Comments

@findepi
Copy link
Member

findepi commented Oct 11, 2021 •
edited
Loading

in #1324 we have a TODO item "Use metastore locking around read-modify-write operations for transaction commit".

Sadly, we didn't inform the users about the limitation (at least i couldn't find it on https://trino.io/docs/current/connector/iceberg.html) , so from user perspective, it's a data loss bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working correctness
Milestone
364
Development

Successfully merging a pull request may close this issue.

Use metastore locking around read-modify-write operations for transaction commit findepi/trino
1 participant
@findepi