You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Aaron Kimball (JIRA)" <ji...@apache.org> on 2009/07/07 03:47:14 UTC

[jira] Reopened: (HADOOP-5482) org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle

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

Aaron Kimball reopened HADOOP-5482:
-----------------------------------


This issue was marked "Resolved" but it was never applied to the 20 branch or trunk (for that matter, it never seems to have gone through Hudson).

I need Oracle support on 20/trunk, so I'm reopening this issue to revisit this patch.

> org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-5482
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5482
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.18.2, 0.18.3, 0.19.0, 0.19.1
>         Environment: Java 1.6, HAdoop0.19.0, Linux..Oracle, 
>            Reporter: evanand
>            Priority: Blocker
>         Attachments: HADOOP-5482.20-branch.patch, HADOOP-5482.patch, HADOOP-5482.trunk.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle.
> The out of the box implementation of the Hadoop is working properly with mysql/hsqldb, but NOT with oracle.
> Reason is DBInputformat is implemented with mysql/hsqldb specific query constructs like "LIMIT", "OFFSET".
> FIX:
> building a database provider specific logic based on the database providername (which we can get using connection).
> I HAVE ALREADY IMPLEMENTED IT FOR ORACLE...READY TO CHECK_IN CODE

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