[
https://issues.apache.org/jira/browse/SQOOP-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188763#comment-13188763
]
Matt Foley commented on SQOOP-384:
----------------------------------
If I could do a 1.0.1 RC in two weeks, would that be fast enough? That gives
Tom time to add the last API and get the patch reviewed, and me time to manage
the build.
When is Hive 0.8.1 expected?
I'm really allergic to putting Hadoop code into sqoop and then saying we'll
remember to take it out later. Let's just do it right the first time. The
projects in this ecosystem have to find a better way to accomodate each other
than by swallowing obsolete chunks of each other :-) BigTop makes a great
forcing function for this, and we shouldn't waste it.
> 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
