hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4191) Add a testcase for jobhistory
Date Tue, 30 Sep 2008 04:37:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635649#action_12635649

Amar Kamat commented on HADOOP-4191:

I am thinking more in terms of a precautionary measure. Instead of creating a history file
and then testing whether it adheres to some schema, it would be nice to catch the incompatible
change early and let the developer know the effect of the changes made. Otherwise the only
way to figure the incompatibility would be see why some of the tests failed and infer the
cause. Someone trying to change the history might know about its effect on job-recovery or

> Add a testcase for jobhistory
> -----------------------------
>                 Key: HADOOP-4191
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4191
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred, test
>            Reporter: Amar Kamat
>             Fix For: 0.19.0
> Changes in job history might break the history parser which in turn might break some
features like jobtracker-recovery, history-viewer etc. There should be a testcase that catches
these incompatible changes early and informs about the expected change.

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

View raw message