You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/01/20 00:07:26 UTC

[jira] [Resolved] (CALCITE-1577) Druid adapter: Incorrect result - limit on timestamp disappears

     [ https://issues.apache.org/jira/browse/CALCITE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-1577.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.12.0

Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/e5c9f2ed.

> 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
>             Fix For: 1.12.0
>
>
> 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)