Add syncer_cursor_at
#1
Closed
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
lucasmrod
force-pushed
the
issue-4-add-cursor-mod-time
branch
from
7a4657b
to
7a81a4b
Compare
This pull request was closed.
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.
We believe this is needed by syncer+assigner for the following scenario:
If all device events have been fetched/synced (thus we have a cursor in storage), and the operator updates the assigner profile UUID, then we would like to re-apply the profile to all devices.
With this change this can be accomplished by comparing the
syncer_cursor_atwithassigner_profile_uuid_at(and remove/clear the cursor from storage if the latter is newer than the former).