chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Yang (JIRA)" <>
Subject [jira] Reopened: (CHUKWA-316) jobconf Error in mr_job_* table
Date Tue, 23 Jun 2009 00:54:07 GMT


Eric Yang reopened CHUKWA-316:

When configuration is specified like this:

  <description>Explicitly undefined jobconf path to load to database</description>

The configuration object will filter out this key.  As a workaround, use configuration like:

  <description>Explicitly undefined jobconf path to load to database</description>

> jobconf Error in mr_job_* table
> -------------------------------
>                 Key: CHUKWA-316
>                 URL:
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: Data Processors
>    Affects Versions: 0.2.0
>         Environment: Redhat EL 5,1, Java 6
>            Reporter: Eric Yang
>            Assignee: Eric Yang
>            Priority: Blocker
>             Fix For: 0.2.0, 0.3.0
>         Attachments: CHUKWA-316.patch
> The current mr_job table, jobconf columns contains the content of jobconf for some rows,
and other rows contains the
> path of the jobconf.
> In the sequence file, jobconf is the field for location of the jobconf path.  The content
of the jobconf is
> JOBCONF-JSON.  In database table, jobconf is the content of the jobconf.  Unfortunately,
the new automatic mapping will
> detect sequence file "jobconf" field is a match with "jobconf" column in the database.
 Hence the
> last update wins.
> To work around this problem, we need ability to undefine sequence file field to match
to database column.
> Personally, I think indirect data translation mapping is the wrong thing to do.  The
mapping should be as straight forward as possible.

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

View raw message