Rong Rong

possibly related: https://github.com/apache/pinot/issues/8045

> This is a great feature! I'd suggest starting a high level design on all the date and time related types, and their behaviors so that we are on the...

> @walterddr @Jackie-Jiang I did a survey of other systems and put the results in this doc: https://docs.google.com/document/d/1Dvz7NJ2eliIFm6O1Ra4Azs_WFWR98kHOyDCznIwaXow/edit# > > My vote is also to follow the Postgres standard, though...

@61yao unfortunately there's no direct equivalence. the currently query timeout logic is: 1. query timeout can be overwritten in this order - user config inside the query payload - table...

+1 on @siddharthteotia 's comment. let's do the following 1. ignore the table level config for multi-stage (at least for now) 2. the rest is exactly the same, make sure...

how did you change the retention period? did you post that as part of the REST API request to delete the segment or did you change the `controller.deleted.segments.retentionInDays` setting after...

this is not something postgres supports (which is much closer following SQL standard) - only `COUNT(DISTINCT( [, ]* )` however given we already support DISTINCTCOUNT, it seems ok to support...

good idea. we also had some feedback from the community on this. but the stats definition is the first to sort out.

CC @nizarhejazi @siddharthteotia

This is the tradition that postgres follows. which is what i know that follows SQL standard the most for aggregation without group by - `SELECT SUM(a) FROM tbl WHERE a...