Skip to content
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

Apply TypeCoercion rule before FilterPushDown #3289

Closed
andygrove opened this issue Aug 29, 2022 · 0 comments · Fixed by #3459
Closed

Apply TypeCoercion rule before FilterPushDown #3289

andygrove opened this issue Aug 29, 2022 · 0 comments · Fixed by #3459
Labels
enhancement New feature or request

Comments

@andygrove
Copy link
Member

andygrove commented Aug 29, 2022

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

#3222 adds a new TypeCoercion rule. The rule is currently applied after filter push down but it could be beneficial to do this earlier. This is a follow on issue to do that work.

We need to implement #3414 first because of these test failures when moving the rule above filter push down:

failures:
    prune_decimal_eq
    prune_decimal_lt
    prune_int32_eq
    prune_int32_lt
    prune_int32_scalar_fun_and_eq

Describe the solution you'd like
As above

Describe alternatives you've considered
None

Additional context
None

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant