[jira] [Resolved] (CALCITE-1579) Druid adapter: wrong semantics of groupBy query limit with granularity

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

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

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

> Druid adapter: wrong semantics of groupBy query limit with granularity
> ----------------------------------------------------------------------
>
>                 Key: CALCITE-1579
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1579
>             Project: Calcite
>          Issue Type: Bug
>          Components: druid
>    Affects Versions: 1.11.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Julian Hyde
>            Priority: Critical
>             Fix For: 1.12.0
>
>
> Similar to CALCITE-1578, but for GroupBy queries. Limit is applied per granularity unit, not globally for the query.
> Currently, the following SQL query infers granularity 'day' for Druid _groupBy_ and pushes the limit, which is incorrect.
> {code:sql}
> SELECT i_brand_id, floor_day(`__time`), max(ss_quantity), sum(ss_wholesale_cost) as s
> FROM store_sales_sold_time_subset
> GROUP BY i_brand_id, floor_day(`__time`)
> ORDER BY s
> LIMIT 10;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)