You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Ramya Sunil (JIRA)" <ji...@apache.org> on 2011/08/10 20:58:27 UTC

[jira] [Created] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

[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
            Priority: Minor
             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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122341#comment-13122341 ] 

Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------

For explanations on why job name "word count" is encoded as "word+count" and safe characters please see the following link.

http://download.oracle.com/javase/6/docs/api/java/net/URLEncoder.html
                
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123468#comment-13123468 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #33 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/33/])
    Merge -c 1180220 from trunk to branch-0.23 to fix MAPREDUCE-2802.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180222
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Updated] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles updated MAPREDUCE-2802:
---------------------------------------

    Status: Patch Available  (was: Open)
    
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123188#comment-13123188 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Common-trunk-Commit #1041 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1041/])
    MAPREDUCE-2802. Ensure JobHistory filenames have jobId. Contributed by Jonathan Eagles.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180220
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hadoop QA (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122404#comment-13122404 ] 

Hadoop QA commented on MAPREDUCE-2802:
--------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12498078/MAPREDUCE-2802.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed unit tests in .

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/961//testReport/
Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/961//console

This message is automatically generated.
                
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122377#comment-13122377 ] 

Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------

+1 overall.  

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs (version ) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123449#comment-13123449 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk #824 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/824/])
    MAPREDUCE-2802. Ensure JobHistory filenames have jobId. Contributed by Jonathan Eagles.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180220
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123191#comment-13123191 ] 

Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------

Thanks so much, Arun!
                
> [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

        

[jira] [Updated] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles updated MAPREDUCE-2802:
---------------------------------------

    Attachment: MAPREDUCE-2802.patch
    
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123490#comment-13123490 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk #854 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/854/])
    MAPREDUCE-2802. Ensure JobHistory filenames have jobId. Contributed by Jonathan Eagles.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180220
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122900#comment-13122900 ] 

Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------

Thanks, Sid!
                
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123482#comment-13123482 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Mapreduce-0.23-Build #40 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/40/])
    Merge -c 1180220 from trunk to branch-0.23 to fix MAPREDUCE-2802.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180222
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Assigned] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Eagles reassigned MAPREDUCE-2802:
------------------------------------------

    Assignee: Jonathan Eagles
    
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Siddharth Seth (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123186#comment-13123186 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #1119 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1119/])
    MAPREDUCE-2802. Ensure JobHistory filenames have jobId. Contributed by Jonathan Eagles.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180220
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123223#comment-13123223 ] 

Hudson commented on MAPREDUCE-2802:
-----------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #1060 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1060/])
    MAPREDUCE-2802. Ensure JobHistory filenames have jobId. Contributed by Jonathan Eagles.

acmurthy : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1180220
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/jobhistory/FileNameIndexUtils.java
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory
* /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/test/java/org/apache/hadoop/mapreduce/v2/jobhistory/TestFileNameIndexUtils.java

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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122342#comment-13122342 ] 

Jonathan Eagles commented on MAPREDUCE-2802:
--------------------------------------------

The patch adds a new test file and directory.
                
> [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

        

[jira] [Commented] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Jonathan Eagles (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated MAPREDUCE-2802:
-------------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

I just committed this. Thanks Jonathan!

(Sid - thanks for the review too!)
                
> [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

        

[jira] [Updated] (MAPREDUCE-2802) [MR-279] Jobhistory filenames should have jobID to help in better parsing

Posted by "Arun C Murthy (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/MAPREDUCE-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun C Murthy updated MAPREDUCE-2802:
-------------------------------------

    Priority: Critical  (was: Minor)

> [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
>            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira