hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4084) Add explain plan capabilities to Hive QL
Date Wed, 17 Sep 2008 21:33:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631959#action_12631959

Ashish Thusoo commented on HADOOP-4084:

looked at this with Dhrubha...

seems like hadoopQA is not able to handle deleted files. UDAFRegistry.java and UDFRegistry.java
have been deleted. But the patch command converts the deletes into empty files and does not
actually remove the files, hence the failure. Is there a more permanent solution to this so
that the patch command is able to delete files. Maybe we should upload the svn stat output
as well to help in this.


> Add explain plan capabilities to Hive QL
> ----------------------------------------
>                 Key: HADOOP-4084
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4084
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: contrib/hive
>            Reporter: Ashish Thusoo
>            Assignee: Ashish Thusoo
>             Fix For: 0.19.0
>         Attachments: patch-4084, patch-4084
> Adding explain plan for queries in hive.
> The current proposal is to support something like:
> SELECT ....
> This will output the following:
> Abstract Syntax Tree:
> Number of Stages:
> Dependencies between Stages:
> Plan for each stage:
> If EXTENDED keyword is used then much more information will be emitted where as without
that keyword only logical information will be emitted.
> e.g. In case of a group by query 
> SELECT T.c1, count(1) FROM T GROUP BY T.c1;
> The explain plan itself has two stages
> Stage1 and Stage2
> Stage1 will have the plan for generating the partial aggregates
> and Stage2 will have the plan for generating the complete aggregates.
> I also plan to convert the parse and semantic analysis tests so that they use this for
finding differences in the plan instead of the programmatic plan dumps that we are using today

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message