hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4955) Make DBOutputFormat us column names from setOutput(...)
Date Mon, 16 Feb 2009 17:02:38 GMT

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

Hudson commented on HADOOP-4955:

Integrated in Hadoop-trunk #756 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/756/])

> Make DBOutputFormat us column names from setOutput(...)
> -------------------------------------------------------
>                 Key: HADOOP-4955
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4955
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.0
>         Environment: Ubuntu 8.04, Java 6, MySQL 5.0 (most likely not relevant)
>            Reporter: Kevin Peterson
>             Fix For: 0.19.1
>         Attachments: hadoop-4955.txt, patch.txt
> In org.apache.hadoop.mapred.lib.db.DBOutputFormat, the supplied names of the columns
are not used for inserting values. The column names supplied to DBOutputFormat.setOutput(JobConf,
String, String...) are used to determine the number of values to insert, but the order is
dictated by the table definition of the underlying database. This affects the correct indices
for DBWritable.write(PreparedStatement).
> I will attach a patch that correctly maps these values.
> I am characterizing this as a bug rather than an improvement because there may be existing
code which implicitly relied on DBOutputFormat ignoring the supplied table names.

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

View raw message