Skip to content

feat: check whether table ops conflict when committing #1816

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

Closed
wants to merge 2 commits into from

Conversation

YinZheng-Sun
Copy link

check whether table ops conflict when committing
related to #1678

Rationale for this change

Are these changes tested?

Are there any user-facing changes?

Comment on lines 248 to 249
except Exception:
return self._transaction._table.metadata
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any specific reason to swallow this exception? If there are any errors, I think it is likely that the commit will fail as well.

Comment on lines +466 to +467
if snapshot is None:
raise CommitFailedException("Snapshot cannot be None.")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is not correct. When you create an empty table, there is no current-snapshot.

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