[
https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122188#comment-13122188
]
Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------
jobids, user names, and job names are sanitized when generating the job history
file name. Since the name of the file needs to be parsed in the current design,
a delimiter, underscore '_', was chosen. When an underscore occurs in the job
id, user name, or job name it is changed to %5F like you are seeing above.
Very simply I can change the delimiter used to lessen the likelihood of percent
encoding to happen. For example, dash '-' would look like this.
job_1317928501754_0001-1317928742025-jeagles-word+count-1317928754958-1-1-SUCCEEDED.jhist
> [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
>
>
> 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
