Skip to content

Apply TypeCoercion rule before FilterPushDown #3289

@andygrove

Description

@andygrove

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions