[
https://issues.apache.org/jira/browse/SQOOP-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188595#comment-13188595
]
Tom White commented on SQOOP-384:
---------------------------------
I think this may be my fault - I didn't open MAPREDUCE-3607 until after this
had gone in (in fact, seeing this work in Sqoop prompted me to submit the MR
fix). Perhaps we can keep this in Sqoop until there is a public Hadoop release
with the new libraries in, at which point we can switch to using them in Sqoop.
Does that sound reasonable?
> Sqoop is incompatible with Hadoop prior to 0.21
> -----------------------------------------------
>
> Key: SQOOP-384
> URL: https://issues.apache.org/jira/browse/SQOOP-384
> Project: Sqoop
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.3.0
> Reporter: Roman Shaposhnik
> Labels: hadoop, patch
> Fix For: 1.4.1-incubating
>
> Attachments: wad_ConfigurationHolder.patch.gz
>
>
> The following are the APIs Sqoop relies upon, which are not available in
> Hadoop prior to 0.21:
> org.apache.hadoop.conf.Configuration.getInstances
> org.apache.hadoop.mapreduce.lib.db.DBWritable
> org.apache.hadoop.mapreduce.lib.input.CombineFileSplit
> org.apache.hadoop.mapreduce.lib.input.CombineFileInputFormat
> org.apache.hadoop.mapreduce.lib.input.CombineFileRecordReader
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
