[ 
https://issues.apache.org/jira/browse/HADOOP-4190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633671#action_12633671
 ] 

Amar Kamat commented on HADOOP-4190:
------------------------------------

Result of test-patch on branch-19
{noformat}
     [exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 6 new or 
modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
{noformat}
Running ant-test.

> Changes to JobHistory makes it backward incompatible
> ----------------------------------------------------
>
>                 Key: HADOOP-4190
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4190
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>            Reporter: Amar Kamat
>            Assignee: Amar Kamat
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: HADOOP-4190-v3.patch, HADOOP-4190-v4.patch, 
> HADOOP-4190-v5.patch
>
>
> With HADOOP-3245, the job history format has changed. Every log line now ends 
> with a '.' (dot). JobHistory's parser will consider a history line valid only 
> if it ends in a dot
> Hence the new parser wont be able to parse old history files.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to