Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 25 Feb 2015 21:29:04 +0000 (UTC)
From: "Pengcheng Xiong (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12777374.1424825860000.14971.1424899744435@Atlassian.JIRA>
In-Reply-To: <JIRA.12777374.1424825860000@Atlassian.JIRA>
References: <JIRA.12777374.1424825860000@Atlassian.JIRA>
 <JIRA.12777374.1424825860560@arcas>
Subject: [jira] [Updated] (HIVE-9780) Add another level of explain for RDBMS
 audience
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pengcheng Xiong updated HIVE-9780:
----------------------------------
    Attachment: HIVE-9780.01.patch

step 1: make the explain level configurable

> Add another level of explain for RDBMS audience
> -----------------------------------------------
>
>                 Key: HIVE-9780
>                 URL: https://issues.apache.org/jira/browse/HIVE-9780
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Pengcheng Xiong
>            Assignee: Pengcheng Xiong
>            Priority: Minor
>         Attachments: HIVE-9780.01.patch
>
>
> Current Hive Explain (default) is targeted at MR Audience. We need a new level of explain plan to be targeted at RDBMS audience. The explain requires these:
> 1) The focus needs to be on what part of the query is being executed rather than internals of the engines
> 2) There needs to be a clearly readable tree of operations
> 3) Examples - Table scan should mention the table being scanned, the Sarg, the size of table and expected cardinality after the Sarg'ed read. The join should mention the table being joined with and the join condition. The aggregate should mention the columns in the group-by. 


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