hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3157) Rumen TraceBuilder is skipping analyzing 0.20 history files
Date Tue, 11 Oct 2011 05:06:30 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13124694#comment-13124694

Amar Kamat commented on MAPREDUCE-3157:

Instead of parsing the current job-history files using JobHistory.CONF_FILENAME_REGEX or JobHistory.JOBHISTORY_FILENAME_REGEX,
should we use the JobHistory's filename parsing APIs like getJobIDFromHistoryFilePath()?
> Rumen TraceBuilder is skipping analyzing 0.20 history files
> -----------------------------------------------------------
>                 Key: MAPREDUCE-3157
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3157
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tools/rumen
>    Affects Versions: 0.23.0
>            Reporter: Ravi Gummadi
>            Assignee: Ravi Gummadi
>             Fix For: 0.23.0
>         Attachments: MR3157.patch
> Rumen TraceBuilder is assuming the Pre21 history file name format to be JTIdentifier_jobId_<something>.
But it can be jobId_<something> also as it is now in latest 0.20.x version. This also
needs to be understood by TraceBuilder.

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


View raw message