-
Notifications
You must be signed in to change notification settings - Fork 20.8k
core/filtermaps: fix log value search range #31734
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
Merged
+16
−7
Merged
Changes from all commits
Commits
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 hidden or 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 hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -82,13 +82,26 @@ func (fm *FilterMapsMatcherBackend) GetFilterMapRow(ctx context.Context, mapInde | |
} | ||
|
||
// GetBlockLvPointer returns the starting log value index where the log values | ||
// generated by the given block are located. If blockNumber is beyond the current | ||
// head then the first unoccupied log value index is returned. | ||
// generated by the given block are located. If blockNumber is beyond the last | ||
// indexed block then the pointer will point right after this block, ensuring | ||
// that the matcher does not fail and can return a set of results where the | ||
// valid range is correct. | ||
// GetBlockLvPointer implements MatcherBackend. | ||
func (fm *FilterMapsMatcherBackend) GetBlockLvPointer(ctx context.Context, blockNumber uint64) (uint64, error) { | ||
fm.f.indexLock.RLock() | ||
defer fm.f.indexLock.RUnlock() | ||
|
||
if blockNumber >= fm.f.indexedRange.blocks.AfterLast() { | ||
if fm.f.indexedRange.headIndexed { | ||
// return index after head block | ||
return fm.f.indexedRange.headDelimiter + 1, nil | ||
} | ||
if fm.f.indexedRange.blocks.Count() > 0 { | ||
// return index at the beginning of the last, partially indexed | ||
// block (after the last fully indexed one) | ||
blockNumber = fm.f.indexedRange.blocks.Last() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If I understand correct, if the requested block beyonds the last indexed block,
// discard everything that might be invalid
trimRange := s.syncRange.ValidBlocks.Intersection(s.chainView.SharedRange(s.syncRange.IndexedView))
matchRange, matches := s.trimMatches(trimRange, r, results)
|
||
} | ||
} | ||
return fm.f.getBlockLvPointer(blockNumber) | ||
} | ||
|
||
|
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.
If the indexed range is fully indexed, the whole range will be available for searching;
If the indexed range is partially indexed (the last one is not fully indexed), then [first, last) will be availabel for searching;