[ 
https://issues.apache.org/jira/browse/SQOOP-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188962#comment-13188962
 ] 

Jarek Jarcec Cecho commented on SQOOP-384:
------------------------------------------

Thank you very much for your comments guys. I really appreciate your feedback. 
I agree that copy&pasting code from core hadoop is weird and MAPREDUCE-3607 is 
far more better way to achieve this goal. 

However works on this JIRA were driven by community need to support also 
version 0.20.2 and 0.20.20X on already deployed clusters. I'm not expecting 
users to upgrade on 1.0(.1) immediately. So I would (as RM for 1.4.1) prefer to 
let this patch in for now and as Tom suggested remove it later when there will 
be no need from community to support those versions. 

Also we recently kicked off works on sqoop 2 which will be complete rewrite of 
the project, so those "backports" will be definitely removed in the future 
anyway.

Does my reasoning make sense to you guys?

Jarcec
                
> 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

        

Reply via email to