Apache Pinot Daily Email Digest (2021-11-14)

Pinot Slack Email Digest Sun, 14 Nov 2021 18:00:25 -0800

#general

@aarti.gaddale187: @aarti.gaddale187 has joined the channel
@mapshen: As per > stream.[streamType].consumer.prop.auto.offset.reset > determines the offset from which to start the ingestion > `smallest` `largest` or timestamp in milliseconds However, it doesn’t seem to take a timestamp?

#random

@contact: @contact has left the channel
@aarti.gaddale187: @aarti.gaddale187 has joined the channel

#troubleshooting

@aarti.gaddale187: @aarti.gaddale187 has joined the channel
@mapshen: 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?
@mayanks: For evaluating the Presto function, it needs the values for col0, right? In that case, what do you mean by push-down?
@mapshen: 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.

#pinot-dev

@aarti.gaddale187: @aarti.gaddale187 has joined the channel

#getting-started