Skip to content

Conversation

@nastra
Copy link
Contributor

@nastra nastra commented Aug 18, 2022

This is related to #5536 and it probably makes sense to let
TableOperations detect that metadata hasn't changed rather than not
calling commit on the operation itself.

This is related to apache#5536 and it probably makes sense to let
`TableOperations` detect that metadata hasn't changed rather than not
calling commit on the operation itself.
@github-actions github-actions bot added the core label Aug 18, 2022
@nastra nastra requested a review from rdblue August 18, 2022 06:44
@rdblue
Copy link
Contributor

rdblue commented Aug 18, 2022

I'm not sure that this makes sense for catalog handlers. It makes sense in operations because the operation may be included in a transaction and need to commit. But that commit will produce the same metadata and the TableOperations will skip making a change in the underlying catalog.

Here, the situation is that a REST service receives a request to update a table with no changes. I think in that case it's perfectly fine to return early and send back 200.

@nastra nastra closed this Aug 19, 2022
@nastra nastra deleted the empty-commits branch August 19, 2022 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants