Skip to content

[FEA] Use optional runtime filtering optimizations in cudf-polars #23576

Description

@rjzamora

Follow up to #22996 and #22997

As suggested by @wence-, we should encode pre-join filter optimizations as a runtime "hint", rather than a "required" logical operation. This way, the cost decision can be done at runtime, when the actors can observe real data properties.

Prerequisites:

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Status
In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions