forked from blevesearch/bleve
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Returning bytesRead as part of searchResult (blevesearch#1752)
* refactoring the bytes read while querying * bug fix: incrementing the bytes read at the right time * bug fix: fixing doc value and stored fields section bytes read computation * - updating stored fields' bytes read logic - bug fixes with respect to bytes read tracking in collector, tfr and docValueReader - fixing boolean searcher's BytesRead() API * - updating TestBytesRead and TestBytesReadStored with numbers after the bug fixes. * - updating the searcher interface and implementations with a SetBytesRead() API. Currently the only valid implmentations is with disjunct and conjunct searchers. - introducing BytesRead for newSnapshotIndexFieldDict. This is necessary for fuzzy, regex like queries. - updating the tests with the changes - updating rest of interface dependencies with no-op APIs in their implementations * - accounting the bytes read for prefix, range regexp queries in the seacher - minor code refactor with respect to tfr * a huge experimental change by introducing the concept of context right at the searcher level. this will essentially help in bytesRead tracking as well. * - using the IOstats reporter callback in term field reader and reporting the same as part of search result. - and yes, it works :D - removed the BytesRead and SetBytesRead API from searcher * - bug fixes with respect bytes read tracking in regexp queries - fixed a race condition around the newSnapshotIndexFieldDict - using the callbacks to return the bytes read value with respect to fieldDict in regexp, fuzzy etc type of queries, where there is a index.FieldDict creation involved (which loads the termDictionary for that field) - updated the tests reflecting the bug fixes. - removing the BytesRead API for index.TermFieldreader * - including the review comments and minor code cleanup * - addressing review comments, minor code cleanup - removing bytesRead from search.DocumentMatch * bug fixes with respect to reporting of the bytesRead * updating test plans * updating go.mod and go.sum * added some comments * minor renaming of function name
- Loading branch information
1 parent
20e6eb5
commit 1643dc3
Showing
90 changed files
with
657 additions
and
450 deletions.
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
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
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.