Jesus Camacho Rodriguez created CALCITE-1577:
Summary: Druid adapter: Incorrect result - limit on timestamp
disappears
Key: CALCITE-1577
URL: https://issues.apache.org/jira/browse/CALCITE-1577
Jesus Camacho Rodriguez created CALCITE-1578:
Summary: Druid adapter: wrong semantics of topN query limit with
granularity
Key: CALCITE-1578
URL: https://issues.apache.org/jira/browse/CALCITE-1578
Jesus Camacho Rodriguez created CALCITE-1579:
Summary: Druid adapter: wrong semantics of groupBy query limit
with granularity
Key: CALCITE-1579
URL: https://issues.apache.org/jira/browse/CALCITE-1579
Jesus Camacho Rodriguez created CALCITE-1580:
Summary: Druid adapter: Wrong semantics for ordering within
groupBy queries
Key: CALCITE-1580
URL: https://issues.apache.org/jira/browse/CALCITE-1580
I don’t understand your requirements exactly, but you should definitely look
into PARTITION BY. It comes up very often in real-life queries.
One way to clarify your requirements is to ask how many records you want your
query to omit. If state has 50 values and your source table has 1M values the
Hi,
I am trying use calcite and develop a custom adapter. I have implemented
the SPI and able to get basic enumerator to work with a simple select query
and no where clause.
Trying to understand how to convert operators to range scan and push them
to the underlying data source.
Should it be a ru
