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

Jason Lowe commented on MAPREDUCE-6160:
---------------------------------------

Thanks for updating the patch.  Patch looks good overall, just one nit.  Should 
we just say "Unknown Job " + jobId for the error message?  That would be 
consistent with the other error messages for tasks and attempts.  
ClientServiceDelegate already logs when it is redirecting to the historyserver, 
so I'm not sure we need to say it's the AM here.  Either that or the task and 
attempt exception messages should be updated for consistency.

> Potential NullPointerException in MRClientProtocol interface implementation.
> ----------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-6160
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6160
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Rohith
>            Assignee: Rohith
>         Attachments: MAPREDUCE-6160.1.patch, MAPREDUCE-6160.2.patch, 
> MAPREDUCE-6160.patch, MAPREDUCE-6160.patch
>
>
> In the implementation of MRClientProtocol, many methods can throw 
> NullPointerExceptions. Instead of NullPointerExceptions, better to throw 
> IOException with proper message.
> In the HistoryClientService class and MRClientService class has 
> #verifyAndGetJob() method that return job object as null.
> {code}
> getTaskReport(GetTaskReportRequest request) throws IOException;
> getTaskAttemptReport(GetTaskAttemptReportRequest request) throws IOException;
> getCounters(GetCountersRequest request) throws IOException;
> getTaskAttemptCompletionEvents(GetTaskAttemptCompletionEventsRequest request) 
> throws IOException;
> getTaskReports(GetTaskReportsRequest request) throws IOException;
> getDiagnostics(GetDiagnosticsRequest request) throws IOException;
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to