fix(core): fix duplicate mutation entries for count index #9208
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.
For calculating length, we want to be able to just look at the mutable layer and not check immutable layer to improve time. For this we had an assumption that we won't have duplicate mutations stored. Turns out, the assumption is only try for index keys, not for the data keys. This PR fixes it for count keys also.
Since duplicate keys can be present in the database right now for people using it from before, we advise to rebuild count index after this upgrade.