Merged
Conversation
blp
approved these changes
Mar 26, 2026
InputUpsert worked incorrectly when updates arrived in multiple batches within a step. In particular when the same key occurs as a delete in the first batch, and an insert in the second batch, we'd apply them in the wrong order. Signed-off-by: Leonid Ryzhyk <ryzhyk@gmail.com>
ryzhyk
force-pushed
the
input-upsert-fix
branch
from
b973d3b to
ff68e51
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
InputUpsert worked incorrectly when updates arrived in multiple batches within
a step. In particular when the same key occurs as a delete in the first batch,
and an insert in the second batch, we'd apply them in the wrong order.
Describe Manual Test Plan
Tested on a customer pipeline that manifested the error.
Checklist