You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading parquet files and/or their metadata, timestamp column metadata statistics stats_min_value and stats_max_value seem to not respect the timestamps configuration of ms, resulting in where filters ignoring entire chunks.
To Reproduce
Example file using ms precision in stats: 2022-11-27T17 42 35.480941703Z.parquet.txt select path_in_schema, stats_min_value, stats_max_value from 'file.parquet'; select * from 'file.parquet'; select * from 'file.parquet' where timestamp < '2022-01-01 00:00:00.000'; select * from 'file.parquet' where timestamp > '2022-01-01 00:00:00.000';
I've verified the raw values in the parquet file before filing this issue.
OS:
Linux-x64 & shell.duckdb.org
DuckDB Version:
0.6.0
DuckDB Client:
rust & wasm
Full Name:
Michl Steglich
Affiliation:
drf.rs
Have you tried this on the latest master branch?
I agree
Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
I agree
The text was updated successfully, but these errors were encountered:
What happens?
When reading parquet files and/or their metadata, timestamp column metadata statistics
stats_min_value
andstats_max_value
seem to not respect the timestamps configuration ofms
, resulting inwhere
filters ignoring entire chunks.To Reproduce
Example file using
ms
precision in stats:2022-11-27T17 42 35.480941703Z.parquet.txt
select path_in_schema, stats_min_value, stats_max_value from 'file.parquet';
select * from 'file.parquet';
select * from 'file.parquet' where timestamp < '2022-01-01 00:00:00.000';
select * from 'file.parquet' where timestamp > '2022-01-01 00:00:00.000';
I've verified the raw values in the parquet file before filing this issue.
OS:
Linux-x64 & shell.duckdb.org
DuckDB Version:
0.6.0
DuckDB Client:
rust & wasm
Full Name:
Michl Steglich
Affiliation:
drf.rs
Have you tried this on the latest
master
branch?Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?
The text was updated successfully, but these errors were encountered: