[
https://issues.apache.org/jira/browse/MAPREDUCE-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14482534#comment-14482534
]
Harsh J commented on MAPREDUCE-6297:
------------------------------------
While the new changes look OK to me otherwise, I notice we're removing a more
specific error for a generic one:
{code}
- "java.lang.Exception: Bad TaskType identifier. TaskId string : "
- + "task_0_0000_d_000000 is not properly formed.", message);
+ "java.lang.Exception: TaskId string : "
+ + "task_0_0000_d_000000 is not properly formed", message);
{code}
Is there a way to add back the task-type error specificity to the RegEx based
parsing that is replacing the existing TaskID.forName logic?
> Task Id of the failed task in diagnostics should link to the task page
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-6297
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-6297
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: jobhistoryserver
> Affects Versions: 2.6.0
> Reporter: Siqi Li
> Assignee: Siqi Li
> Priority: Minor
> Attachments: 58CCA024-7455-4A87-BCFD-C88054FF841B.png,
> MAPREDUCE-6297.v1.patch, MAPREDUCE-6297.v2.patch, MAPREDUCE-6297.v3.patch,
> MAPREDUCE-6297.v4.patch
>
>
> Currently we have to copy it and search in the task list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
