When querying Pinot via Trino, it seems aggregate pushdowns won’t work for

count(*)

if trino functions are in the predict. For example, the query below doesn’t work and returns an error due to the max rows per split setting:

select count(*) from table0 where from_unixtime(col0) > current_timestamp

but the following query works:

select count(*) from table0 where col0 > 0

Suspect it has something to do with the order of evaluation. Perhaps the trino functions should be evaluated before determining if push downs should happen?

For evaluating the Presto function, it needs the values for col0, right? In that case, what do you mean by push-down?

Yeah, i think you are right. There are two trino functions in the first query,

from_unixtime

and

current_timestamp

. Was focusing on the latter and hence thought if it could be evaluated first, the push-down would happen, but didn’t notice the former require the values of col1.