[
https://issues.apache.org/jira/browse/CALCITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830551#comment-15830551
]
Julian Hyde commented on CALCITE-1577:
--------------------------------------
Your fix looks good. After I applied on top of my fix to CALCITE-1578 et al,
the sort got pulled up out of Druid, so the explain changed, and I was able to
execute the query without Druid blowing up. So I added {{.returnsOrdered}} to
the test cases; that should give us more confidence if we need to maintain the
test in future. Will commit shortly, when the suite passes.
> Druid adapter: Incorrect result - limit on timestamp disappears
> ---------------------------------------------------------------
>
> Key: CALCITE-1577
> URL: https://issues.apache.org/jira/browse/CALCITE-1577
> Project: Calcite
> Issue Type: Bug
> Components: druid
> Affects Versions: 1.11.0
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Priority: Critical
>
> This can be observed with the following query:
> {code:sql}
> SELECT DISTINCT `__time`
> FROM store_sales_sold_time_subset
> ORDER BY `__time` ASC
> LIMIT 10;
> {code}
> Query is translated to Druid _timeseries_, but _limit_ operator disappears.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
