-
Notifications
You must be signed in to change notification settings - Fork 559
[GLUTEN-9849][VL] Reenable native might_contain evaluation that was disabled in #9850
#10240
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
Conversation
|
Run Gluten ClickHouse CI on ARM |
|
@wForget @jinchengchenghh Thanks |
|
Run Gluten ClickHouse CI on ARM |
|
Run Gluten ClickHouse CI on ARM |
|
Run Gluten ClickHouse CI on ARM |
|
Run Gluten ClickHouse CI on ARM |
|
Run Gluten ClickHouse CI on ARM |
| extends BinaryExpression | ||
| with GlutenTaskOnlyExpression { | ||
| extends BinaryExpression { | ||
| import VeloxBloomFilterMightContain._ |
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.
Do we import here?
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.
Yes, for SerializableDirectByteBuffer.
wForget
left a comment
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.
LGTM, thanks.
|
Thanks @wForget @jinchengchenghh! |
Following: #9850
Velox PR needed: facebookincubator/velox#13955
In #9850 we have disabled native
might_containin some cases where the expression is evaluated on Spark driver.The patch uses static evaluation of
might_containfor such cases and re-enable the native code path.