Skip to content

fix(datafusion): classify filter pushdown accurately#2848

Open
AndreaBozzo wants to merge 1 commit into
apache:mainfrom
AndreaBozzo:fix/2363-exact-filter-pushdown
Open

fix(datafusion): classify filter pushdown accurately#2848
AndreaBozzo wants to merge 1 commit into
apache:mainfrom
AndreaBozzo:fix/2363-exact-filter-pushdown

Conversation

@AndreaBozzo

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

What changes are included in this PR?

Classify DataFusion filter pushdown as Exact, Inexact, or Unsupported based on whether conversion to an Iceberg predicate is lossless. Exact filters no longer require a residual FilterExec; conservative and partial conversions remain inexact, and unsafe negated partial conversions remain unsupported.

Are these changes tested?

Yes. Added unit and integration coverage for exact, inexact, and unsupported classifications, and updated SQL logic test expectations.

Validated with:

  • cargo fmt --all -- --check
  • cargo clippy -p iceberg-datafusion --all-targets --all-features -- -D warnings
  • cargo test -p iceberg-datafusion --all-features
  • cargo test -p iceberg-sqllogictest --test sqllogictests

@AndreaBozzo
AndreaBozzo marked this pull request as ready for review July 18, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IcebergTableProvider::supports_filters_pushdown marks every filter as Inexact, causing a redundant FilterExec above IcebergTableScan

1 participant