[ https://issues.apache.org/jira/browse/MAPREDUCE-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140255#comment-13140255 ]
Hudson commented on MAPREDUCE-3166: ----------------------------------- Integrated in Hadoop-Common-0.23-Commit #112 (See [https://builds.apache.org/job/Hadoop-Common-0.23-Commit/112/]) MAPREDUCE-3166. [Rumen] Make Rumen use job history api instead of relying on current history file name format. (Ravi Gummadi via amarrk) amarrk : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1195540 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/ivy.xml * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/test/mapred/org/apache/hadoop/tools/rumen/TestRumenJobTraces.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/src/tools/org/apache/hadoop/tools/rumen/JobHistoryUtils.java > Make Rumen use job history api instead of relying on current history file > name format > ------------------------------------------------------------------------------------- > > Key: MAPREDUCE-3166 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3166 > 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: MR3166.patch > > > Rumen should not depend on the regular expression of job history file name > format and should use the newly added api like isValidJobHistoryFileName(), > getJobIDFromHistoryFilePath(). -- 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