Repository navigation
CAST statistics can produce incorrect MIN/MAX results #25221
Description
Describe the bug
Casting string min/max statistics to integers does not preserve their ordering. Aggregate optimization can therefore return incorrect results.
To Reproduce
SET datafusion.execution.target_partitions = 1;
SET datafusion.execution.collect_statistics = true;
COPY (SELECT * FROM (VALUES ('1'), ('100'), ('2')) AS t(a))
TO '/tmp/cast_statistics.parquet' STORED AS PARQUET;
CREATE EXTERNAL TABLE t STORED AS PARQUET
LOCATION '/tmp/cast_statistics.parquet';
SELECT MIN(CAST(a AS INT)), MAX(CAST(a AS INT)) FROM t;Actual: 1, 2. Expected: 1, 100. The same issue occurs with BIGINT.
Expected behavior
Only propagate CAST statistics when the conversion is proven safe for the supplied bounds.
Additional context
found this when work on #25220
Activity
haohuaijin commentedon Sep 12, 2026
take
fix: only propagate cast statistics through safe conversions (apache#…
fix: only propagate cast statistics through safe conversions (apache#…
fix: only propagate cast statistics through safe conversions (apache#…