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

Posted to issues@hive.apache.org by "Ashutosh Chauhan (JIRA)" <ji...@apache.org> on 2017/04/18 22:19:42 UTC

[jira] [Updated] (HIVE-16358) Push TOP N to Druid queries

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

Ashutosh Chauhan updated HIVE-16358:
------------------------------------
    Target Version/s: 3.0.0

> Push TOP N to Druid queries
> ---------------------------
>
>                 Key: HIVE-16358
>                 URL: https://issues.apache.org/jira/browse/HIVE-16358
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning, Query Processor
>            Reporter: Remus Rusanu
>            Assignee: Remus Rusanu
>
> After HIVE-15708 promotes Calcite to 1.12, {{TOP N}} queries over Druid tables will be implemented by GroupBy on Druid and then (sort and) Limit on Hive. The relevant changes on Calcite side are related to CALCITE-1578 and steam from fundamental semantic differences between Druid concept of TOP (ie. top within a GBy) vs. SQL TOP/LIMIT (ie. global).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)