-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[dbnode] Extend lifetime of compactable index segments for aggregate queries #2550
Merged
robskillington
merged 18 commits into
master
from
r/extend-lifetime-segments-during-aggregate-query
Aug 22, 2020
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
febfec9
[dbnode] Extend lifetime of index segments for aggregate queries
robskillington d0163bd
Merge branch 'master' into r/extend-lifetime-segments-during-aggregat…
robskillington 798f10e
Fix query
robskillington 6a16c30
Remove unused method to close reader async from index/block
robskillington 9d7ff40
Fix index results in tests.
notbdu e091bc4
Fix assertions in unit tests.
notbdu 0d113f9
Fix peers bs tests.
notbdu 9d69dbd
Fix unit test.
notbdu a47a2b5
Add freemmap test
robskillington f444d51
Merge branch 'r/extend-lifetime-segments-during-aggregate-query' of g…
robskillington 7e866f5
Avoid segment is closed error by using readers instead of segments to…
robskillington 77a9c1b
Update mocks
robskillington fc0a381
Fix storage/index tests
robskillington e76cafa
Fix mem segment tests
robskillington d6b98ee
Fix import order
robskillington 176aa29
Fix big unit tests
robskillington 0323478
Fix integ tests
robskillington 5158435
Add rlock/runlock to fsSegment call
robskillington File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the aggregate query trigger the already compacted fst segment iteration bug?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, yes - this was only present for Aggregate queries using "AddSegments(...)". "AddReaders(...)" using the vanilla index query path was already protected since it uses a reader under the hood and doesn't close it until the end of a query (when the search executor closes).