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 "evanand (JIRA)" <ji...@apache.org> on 2009/03/13 00:20:50 UTC

[jira] Updated: (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 ]

evanand updated HADOOP-5482:
----------------------------

    Hadoop Flags: [Reviewed]
          Status: Patch Available  (was: Open)

enhancing org.apache.hadoop.mapred.lib.db.DBInputformat database provider specific logic for oracle based on the database providername

> 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 Core
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.19.1, 0.19.0
>         Environment: Java 1.6, HAdoop0.19.0, Linux..Oracle, 
>            Reporter: evanand
>            Priority: Blocker
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> 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.