perf(query) Use the last chunk and avoid scan if the data is available in the latest ingesting chunk #1978
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
…le in the latest ingesting chunk
amolnayak311
changed the title
…e in the latest ingesting chunk
vishramachandran
approved these changes
Mar 25, 2025
amolnayak311
added a commit
to amolnayak311/FiloDB
that referenced
this pull request
Mar 25, 2025
…e in the latest ingesting chunk (filodb#1978)
amolnayak311
added a commit
to amolnayak311/FiloDB
that referenced
this pull request
Mar 25, 2025
…e in the latest ingesting chunk (filodb#1978)
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.
Pull Request checklist
When TimeRangeChunkScan is provided, all chunkInfos are iterated and the relevant ChunkSetInfos are filtered that contains the data for the given range. The change will avoid this scan and first check if the requested data is available in the currentInfo and return that one chunk of interest.
New behavior :
Just return the currentInfo if thats where all the requested data range lies.