[
https://issues.apache.org/jira/browse/MAPREDUCE-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190942#comment-13190942
]
Ravi Gummadi commented on MAPREDUCE-3597:
-----------------------------------------
The above commit messages for branch-0.23 say that the 3 .gz files are
modified. So commit seems to be fine, but the patch uploaded here in JIRA seems
to be missing these files' changes. I will upload a patch for branch-0.23,
which actually got committed and is correct.
> Provide a way to access other info of history file from Rumentool
> -----------------------------------------------------------------
>
> Key: MAPREDUCE-3597
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3597
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tools/rumen
> Affects Versions: 0.24.0
> Reporter: Ravi Gummadi
> Assignee: Ravi Gummadi
> Fix For: 0.24.0
>
> Attachments: 3597.branch-1.v1.patch, 3597.branch-1.v2.patch,
> 3597.v0.patch, 3597.v1.patch, MAPREDUCE-3597_branch-0.23.patch
>
>
> As the trace file generated by Rumen TraceBuilder is skipping some of the
> info like job counters, task counters, etc. we need a way to access "other
> info available in history file which is not dumped to trace file". This is
> useful for components which want to parse history files and get info. These
> components can directly use/leverage "Rumen's parsing of history files across
> hadoop releases" and get history info in a consistent way for further
> analysis/processing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira