[
https://issues.apache.org/jira/browse/MAPREDUCE-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Kimball updated MAPREDUCE-716:
------------------------------------
Attachment: MAPREDUCE-716.3.trunk.patch
New version of the patch which includes changes to keep o.a.h.mapred.lib.db.*
in compliance. Since various interfaces are now abstract classes, I've added a
wrapper which translates the calls from the old RecordReader interface to the
old DBRecordReader into the corresponding calls to the new DBRecordReader
implementations. This has the unfortunate side-effect of requiring some
deprecated methods to be made public again instead of protected in the
new-package DBRecordReader. I don't know a better way around this issue though.
> org.apache.hadoop.mapred.lib.db.DBInputformat not working with oracle
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-716
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-716
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Environment: Java 1.6, HAdoop0.19.0, Linux..Oracle,
> Reporter: evanand
> Assignee: Aaron Kimball
> Attachments: HADOOP-5482.20-branch.patch, HADOOP-5482.patch,
> HADOOP-5482.trunk.patch, MAPREDUCE-716.2.branch20.patch,
> MAPREDUCE-716.2.trunk.patch, MAPREDUCE-716.3.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.
