You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2008/05/09 01:48:57 UTC
[jira] Commented: (HADOOP-2536) MapReduce for MySQL
[ https://issues.apache.org/jira/browse/HADOOP-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595428#action_12595428 ]
Owen O'Malley commented on HADOOP-2536:
---------------------------------------
I'm sorry this bug seems to have been forgotten. I'd suggest putting the code into org.apache.hadoop.mapred.lib.jdbc.*
I'd suggest getting rid of the JDBCMapper and JDBCReducer and moving the initJob into a static method of the JDBCInputFormat and OutputFormat. So have,
{code}
public static void setInput(JobConf job,
String table,
JDBCField keyField,
JDBCField[] fields) { ... }
{code}
and a corresponding setOutput method in JDBCOutputFormat. The preferred style is to have getters and setters rather than public constants of the strings for the configuration.
You should also use your own property for the table name rather than input/output path, because that might be confusing.
> MapReduce for MySQL
> -------------------
>
> Key: HADOOP-2536
> URL: https://issues.apache.org/jira/browse/HADOOP-2536
> Project: Hadoop Core
> Issue Type: New Feature
> Components: mapred
> Reporter: Fredrik Hedberg
> Priority: Minor
> Attachments: hadoop-jdbc.tar.gz, Test.java
>
>
> Add support for running MapReduce jobs over data residing in a MySQL table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.