[MongoDB] Skip current_data storage #129
Merged
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.
Builds on #121.
The current_data bucket storage collection stores the following data:
buckets
: The current set of buckets for each replicated rowlookups
: Current parameter query lookups for each replicated rowdata
: A copy of the current dataBuckets and lookups are used to be able to do REMOVE operations (need to know in which buckets a row was before, so we know from which buckets we need to remove it from after an update).
The
data
bit is to support partial updates. For Postgres, this could be when we receive an update with unchanged TOAST columns. However, for MongoDB we get the full document on each update, so never need that. This adds an optimization for MongoDB to skip that persistence.