[
https://issues.apache.org/jira/browse/HADOOP-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589652#action_12589652
]
Amareshwari Sriramadasu commented on HADOOP-3263:
-------------------------------------------------
Doing not-null check in jobhistory.jsp makes more sense than jobHistory.java,
since jobHistory.java can truncate the filename (if it exceeds
max_file_name_size) and jsp file should take care of that.
> job history browser throws exception if job name or user name is null.
> ----------------------------------------------------------------------
>
> Key: HADOOP-3263
> URL: https://issues.apache.org/jira/browse/HADOOP-3263
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.17.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.17.0
>
> Attachments: patch-3263.txt
>
>
> Job history browser throws exception if job name or user name is null.
> Instead it should print a null string for user/job name if they are null.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
