Filter scope on MongoDB-driver side. #659 #680
Merged
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
afalaleev
force-pushed
the
659-filter-scope-in-mongodb-driver
branch
from
e3185f2
to
f2f5aef
Compare
s-medvedev
approved these changes
May 16, 2019
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.
Resolve #659:
Filtering of scope by MongoDB server is very slow operation for case of big tables, because if collection doesn't contain objects w/
scope, that is requires full-scan of the collection.Alternative way is to use min/max operators of MongoDB and filter
scopeon nodeos-side. If the located object by min/max has otherscope, the mongodb-driver interpret it as end-of-cursor.