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

Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (Jira)" <ji...@apache.org> on 2020/07/24 02:10:00 UTC

[jira] [Commented] (HIVE-23736) Disable topn in ReduceSinkOp if a TNK is introduced

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

Jesus Camacho Rodriguez commented on HIVE-23736:
------------------------------------------------

+1

> Disable topn in ReduceSinkOp if a TNK is introduced
> ---------------------------------------------------
>
>                 Key: HIVE-23736
>                 URL: https://issues.apache.org/jira/browse/HIVE-23736
>             Project: Hive
>          Issue Type: Improvement
>          Components: Physical Optimizer
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Both the Reduce Sink and TopNKey operator has Top n key filtering functionality. If TNK is introduced this functionality is done twice.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)