[
https://issues.apache.org/jira/browse/CALCITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15830509#comment-15830509
]
Julian Hyde commented on CALCITE-1577:
--------------------------------------
Can you create a PR in https://github.com/apache/calcite/pulls and close the
one in https://github.com/julianhyde/calcite/pulls (I don't believe that it's a
valid "contribution" unless the PR is to Apache, so I would not be able to
commit, you would have to.)
I don't see your PR for CALCITE-1578, but in any case, I am just about to check
in a commit which fixes CALCITE-1578, CALCITE-1579 and CALCITE-1580, and
another commit which fixes CALCITE-1587. I do not have time to fix CALCITE-1591
just now.
I'll review your fix shortly.
> 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)
