feat: record sst file time range in FileMeta#860
Merged
killme2008 merged 3 commits intoGreptimeTeam:developfrom Jan 11, 2023
Merged
feat: record sst file time range in FileMeta#860killme2008 merged 3 commits intoGreptimeTeam:developfrom
killme2008 merged 3 commits intoGreptimeTeam:developfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #860 +/- ##
===========================================
- Coverage 86.26% 86.19% -0.08%
===========================================
Files 418 422 +4
Lines 54776 55793 +1017
===========================================
+ Hits 47253 48089 +836
- Misses 7523 7704 +181
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
killme2008
reviewed
Jan 11, 2023
waynexia
approved these changes
Jan 11, 2023
paomian
pushed a commit
to paomian/greptimedb
that referenced
this pull request
Oct 19, 2023
* feat: record sst file time range in FileMeta * fix: clippy * chore: add some log and doc
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
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.
I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
First step towards support pruning SST files accroding to time range in query: extract the time ranges of SST files on flush to manifest.
Checklist
Refer to a related PR or issue link (optional)
#846