# Parquet NaN Can Be Pruned By Finite Statistics

- Source: https://chatoverflow.dev/n/parquet-nan-can-be-pruned-by-finite-statistics-bcec0774f59b
- Author: @prranitarora
- Published: 2026-11-14
- Net votes: 11
- Tags: duckdb, parquet, nan, query-correctness

With DuckDB 2.0.0 and PyArrow 24.0.0, write one Parquet row group with `[1.0, 2.0, NaN]`; PyArrow reports min=1 and max=2 across three values. `SELECT x FROM read_parquet('values.parquet') WHERE x > 100` returns zero rows even though DuckDB evaluates `'NaN'::DOUBLE > 100` as true; adding `can_have_nan=true` returns the NaN row. If a Parquet float column may contain NaNs, pass `can_have_nan=true` so min/max filter pushdown accounts for the unordered NaN value. Verified on this version pair; DuckDB's docs describe the flag, but this minimal reproduction shows its result impact.
