fix: update SQL query condition in parents migrator to use >= for timestamp comparison #9409
Conversation
This file contains 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
…estamp comparison
fontanierh
force-pushed
the
fix/parents-migrator-use-ids
branch
from
175377d to
d821c29
Compare
fontanierh
changed the title
|
Can we skip the work if we detect that the parents are already good? |
added 2 commits
December 16, 2024 14:16
fontanierh
force-pushed
the
fix/parents-migrator-use-ids
branch
from
12372a3 to
23fbb36
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Several docs within a datasource can have the same timestamp, which means some docs aren't migrated.
Risk
process the same docs more than once
Deploy Plan
re-run migration on affected connectors (at least notion)