Open
Description
Given an Iceberg table that is partitioned on day(timestamp_column), I would expect, when doing SELECT min(timestamp_column), max(timestamp_column) from my table, that Trino would look at partitioning, figure out that the min value lives in the first partition and the max value lives in the latest partition and just scan those partitions.
Instead, at the moment all values of that column are scanned.
This was valid for version 475
Metadata
Metadata
Assignees
Labels
No labels