You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2016/09/15 04:54:21 UTC

[jira] [Resolved] (CALCITE-1357) Recognize Druid Timeseries and TopN queries in DruidQuery

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

Jesus Camacho Rodriguez resolved CALCITE-1357.
----------------------------------------------
       Resolution: Fixed
    Fix Version/s: 1.9.0

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

Thanks for the review [~julianhyde]!

Still thinking about your comment around user vs Druid timezone... I will update the issue with some comments shortly.

> Recognize Druid Timeseries and TopN queries in DruidQuery
> ---------------------------------------------------------
>
>                 Key: CALCITE-1357
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1357
>             Project: Calcite
>          Issue Type: Bug
>          Components: druid
>    Affects Versions: 1.9.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 1.9.0
>
>
> Port the work done in HIVE-14217 to recognize Timeseries and TopN queries to Calcite.
> This includes a rule to push SortLimit into DruidQuery, which can lead to creating TopN queries. This rule can help to push sorting and limit into GroupBy queries, and limit to Select queries.



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