-
Notifications
You must be signed in to change notification settings - Fork 970
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
The data type of predicate in the row filter should be same in the binary expr #3469
Comments
why not build the |
If the table schema is c1,c2,c3, the file schema is c1,c3 with filter c2 = lit. Why not push the |
seems like a reasonable thing to me |
|
I think the more general flow here is to take a predicate like Then the predicate is |
@alamb @thinkharderdev
I find a issue caused by this rewrite in my work #3396
if we have two parquet, one has c1,c2, the other has c1,c3.
If the filter is c2 = 1, then it will produce a expr NULL = 1 for the parquet with c1,c3 column.
After I remove the binary type coercion in the physical phase, the binary physical expr of
NULL = INT(1)
can't be created, because we don't need to support type coercion in creation physical expr.Originally posted by @liukun4515 in #3380 (comment)
The text was updated successfully, but these errors were encountered: