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:05:44 GMT

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

Amar Kamat commented on HADOOP-4191:

My intention behind this was to safeguard the framework against unexpected changes in jobhistory.
Some features heavily use jobhistory to get things done. Any incompatible change to jobhistory
might break the framework or render these features useless. Here are few things related to
jobhistory that are assumed
1) jobhistory filename
2) jobhistory file location(s)
3) versioning .. handled in HADOOP-4190
4) jobhistory format
5) jobhistory line structure
6) jobhistory line content i.e keys and values
7) Features like job-recovery expect few fields to be present in a line. Any change to do
with removal of these fields or changing their content/representation should be detected.

> 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