[
https://issues.apache.org/jira/browse/HIVE-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643562#comment-13643562
]
Hudson commented on HIVE-3708:
------------------------------
Integrated in Hive-trunk-h0.21 #2080 (See
[https://builds.apache.org/job/Hive-trunk-h0.21/2080/])
HIVE-3708 : Add mapreduce workflow information to job configuration (Billie
Rinaldi via Ashutosh Chauhan) (Revision 1476252)
Result = FAILURE
hashutosh :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1476252
Files :
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/Driver.java
* /hive/trunk/ql/src/java/org/apache/hadoop/hive/ql/exec/Utilities.java
> Add mapreduce workflow information to job configuration
> -------------------------------------------------------
>
> Key: HIVE-3708
> URL: https://issues.apache.org/jira/browse/HIVE-3708
> Project: Hive
> Issue Type: Improvement
> Reporter: Billie Rinaldi
> Assignee: Billie Rinaldi
> Fix For: 0.12.0
>
> Attachments: HIVE-3708_1.patch, HIVE-3708.patch, HIVE-3708.patch
>
>
> Adding workflow properties to the job configuration would enable logging and
> analysis of workflows in addition to individual MapReduce jobs. Suggested
> properties include a workflow ID, workflow name, adjacency list connecting
> nodes in the workflow, and the name of the current node in the workflow.
> mapreduce.workflow.id - a unique ID for the workflow, ideally prepended with
> the application name
> e.g. hive_<hiveQueryId>
> mapreduce.workflow.name - a name for the workflow, to distinguish this
> workflow from other workflows and to group different runs of the same workflow
> e.g. hive query string
> mapreduce.workflow.adjacency - an adjacency list for the workflow graph,
> encoded as mapreduce.workflow.adjacency.<source node> = <comma-separated list
> of target nodes>
> mapreduce.workflow.node.name - the name of the node corresponding to this
> MapReduce job in the workflow adjacency list
--
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
