hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-16358) Push TOP N to Druid queries
Date Tue, 18 Apr 2017 22:19:42 GMT

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

Ashutosh Chauhan commented on HIVE-16358:
-----------------------------------------

We likely don't need this after CALCITE-1758 

We can still consider HIVE-16121 if there still a usecase left after CALCITE-1758 Will there
be any such case: [~bslim] , [~jcamachorodriguez] ?


> 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)

Mime
View raw message