-
Notifications
You must be signed in to change notification settings - Fork 0
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
OTF-2326 push updates for greater than #2
base: feature/otf-1500_column_comparisons_1521
Are you sure you want to change the base?
OTF-2326 push updates for greater than #2
Conversation
return ROWS_MIGHT_MATCH; | ||
} | ||
|
||
if (checkLowerToUpperBounds(ref, ref2, id, id2, cmp -> cmp > 0)) { |
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.
when data is equal the lower to upper bound checks return that rows cannot match when they can, removing checks. I have updated my test bteqs for this. These impact data pruning and not file pruning
@@ -329,16 +329,16 @@ public <T> Boolean gtEq(BoundReference<T> ref, BoundReference<T> ref2) { | |||
int pos = Accessors.toPosition(ref.accessor()); | |||
int pos2 = Accessors.toPosition(ref2.accessor()); | |||
ByteBuffer upperBound = stats.get(pos).upperBound(); | |||
ByteBuffer upperBound2 = stats.get(pos2).upperBound(); |
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.
correction specific to greater than or equals
I expanded my test case bteqs with equals and found a few of the checks could result in no data being returned.