hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing
Date Fri, 07 Oct 2011 14:15:29 GMT

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

Siddharth Seth commented on MAPREDUCE-2802:
-------------------------------------------

lgtm. NB +1.
Changing the delimiter may be an issue for some apps - but the .23 jobhistory filename has
anyway changed, and there are APIs available to pull information from the filename.
                
> [MR-279] Jobhistory filenames should have jobID to help in better parsing 
> --------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2802
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2802
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Ramya Sunil
>            Assignee: Jonathan Eagles
>            Priority: Critical
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2802.patch
>
>
> For jobID such as job_1312933838300_0007, jobhistory file names are named as job%5F1312933838300%5F0007_<submit_time>_ramya_<jobname>_<finish_time>_1_1_SUCCEEDED.jhist
It would be easier for parsing if the jobIDs were a part of the filenames.

--
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

        

Mime
View raw message