hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Peterson (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-4955) Make DBOutputFormat us column names from setOutput(...)
Date Tue, 30 Dec 2008 02:11:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-4955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kevin Peterson updated HADOOP-4955:
-----------------------------------

    Status: Patch Available  (was: Open)

Let me know if I need to regenerate the patch in a different format.

> 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
>         Attachments: 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.


Mime
View raw message