hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3610) Add a command "Explain dependency ..."
Date Wed, 09 Jan 2013 10:26:36 GMT

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

Hudson commented on HIVE-3610:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3610. Add a command "Explain dependency ..." (Sambavi Muthukrishnan via kevinwilfong)
(Revision 1403467)

     Result = ABORTED
kevinwilfong : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1403467
Files : 
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/ExplainTask.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/ExplainSemanticAnalyzer.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/parse/Hive.g
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/plan/ExplainWork.java
* /hive/trunk/ql/src/test/queries/clientpositive/explain_dependency.q
* /hive/trunk/ql/src/test/results/clientpositive/explain_dependency.q.out

                
> Add a command "Explain dependency ..."
> --------------------------------------
>
>                 Key: HIVE-3610
>                 URL: https://issues.apache.org/jira/browse/HIVE-3610
>             Project: Hive
>          Issue Type: New Feature
>          Components: Query Processor
>    Affects Versions: 0.9.0
>            Reporter: Sambavi Muthukrishnan
>            Assignee: Sambavi Muthukrishnan
>            Priority: Minor
>             Fix For: 0.10.0
>
>         Attachments: explain_dependency.1.patch, explain_dependency.2.patch
>
>
> Add a new command "EXPLAIN DEPENDENCY".
> Any query can be passed to EXPLAIN DEPENDENCY as with EXPLAIN (FORMATTED/EXTENDED). The
output of this command will be JSON that provides the list of tables and partitions that the
query depends on.
> One possible use case is to determine the set of tables/views that are used by a view,
and the set of partitions that are used by a given query on that view. This will allow a view
to be replicated from one Hive instance to another, since we can determine the set of objects
that need to be replicated for replication of the view to be successful.
> Example output:
> {"input_tables":[{"tablename": "default@test_sambavi_v2", "tabletype": "EXTERNAL_TABLE"},
{"tablename": "default@test_sambavi_v1", "tabletype": "TABLE"}], "input partitions":["default@srcpart@ds=2008-04-08/hr=11","default@srcpart@ds=2008-04-08/hr=12"]}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message