Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Sun, 20 Oct 2013 16:08:42 +0000 (UTC)
From: "Chun Chen (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12670429.1380095161611.94336.1382285322317@arcas>
In-Reply-To: <JIRA.12670429.1380095161611@arcas>
References: <JIRA.12670429.1380095161611@arcas>
Subject: [jira] [Updated] (HIVE-5358) ReduceSinkDeDuplication should ignore
 column orders when check overlapping part of keys between parent and child
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chun Chen updated HIVE-5358:
----------------------------

    Status: Open  (was: Patch Available)

> ReduceSinkDeDuplication should ignore column orders when check overlapping part of keys between parent and child
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-5358
>                 URL: https://issues.apache.org/jira/browse/HIVE-5358
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Chun Chen
>            Assignee: Chun Chen
>         Attachments: D13113.1.patch, HIVE-5358.2.patch, HIVE-5358.3.patch, HIVE-5358.patch
>
>
> {code}
> select key, value from (select key, value from src group by key, value) t group by key, value;
> {code}
> This can be optimized by ReduceSinkDeDuplication
> {code}
> select key, value from (select key, value from src group by key, value) t group by value, key;
> {code}
> However the sql above can't be optimized by ReduceSinkDeDuplication currently due to different column orders of parent and child operator.


--
This message was sent by Atlassian JIRA
(v6.1#6144)