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 2016/04/22 02:42:12 UTC

[jira] [Commented] (CALCITE-1206) Push HAVING, ORDER BY and LIMIT into Druid

    [ https://issues.apache.org/jira/browse/CALCITE-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253091#comment-15253091 ] 

Julian Hyde commented on CALCITE-1206:
--------------------------------------

Consider using "topN" Druid queries if the SQL query is of the right form. Druid's documentation claims that they are more efficient. (However, they may be approximate.)

> Push HAVING, ORDER BY and LIMIT into Druid
> ------------------------------------------
>
>                 Key: CALCITE-1206
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1206
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> Push HAVING, ORDER BY and LIMIT into Druid. This extends the basic Druid adapter added in CALCITE-1121.



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