fix: timestamp range filter #2533
Merged
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
v0y4g3r
force-pushed
the
fix/time-range-filter
branch
from
1c991ca to
79e8359
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #2533 +/- ##
===========================================
- Coverage 85.32% 85.02% -0.30%
===========================================
Files 730 731 +1
Lines 116311 116886 +575
===========================================
+ Hits 99240 99384 +144
- Misses 17071 17502 +431 |
evenyag
reviewed
Oct 7, 2023
evenyag
approved these changes
Oct 8, 2023
paomian
pushed a commit
to paomian/greptimedb
that referenced
this pull request
Oct 19, 2023
* fix: timestamp range filter * fix: rebase develop * fix: some style issues
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?
This PR fixes the bug in building timestamp range predicates when operators do not conform commutative property.
Checklist
Refer to a related PR or issue link (optional)
Fixes #2508