[
https://issues.apache.org/jira/browse/BIGTOP-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690943#comment-13690943
]
Roman Shaposhnik commented on BIGTOP-1016:
------------------------------------------
Sorry for coming late to the party, but is there any chance to sync up with the
Sqoop 2 community and figure out what we can do to help bring Sqoop 1.99 all
the way to Sqoop 2 status? Bigtop has already contributed quite a bit in terms
of integration testing of Sqoop 2, may be we need just a tiny push to make
Sqoop 2 a reality.
> Add a new package to bring back Sqoop 1.4.x
> -------------------------------------------
>
> Key: BIGTOP-1016
> URL: https://issues.apache.org/jira/browse/BIGTOP-1016
> Project: Bigtop
> Issue Type: New Feature
> Affects Versions: 0.7.0
> Reporter: Andrew Purtell
>
> On dev@bigtop, Venkat Ranganathan wrote in to say:
> {quote}
> While I understand the motivation behind moving on with Sqoop2 based
> releases (I was part of the 1.99.2 release) Sqoop 1.99.x is an evolving
> preview release and I think it would make it easier for Sqoop users if
> we have both Sqoop2 and Sqoop 1.x available until there is some more
> feature parity. It may be a specific situation with Sqoop project alone
> with two releases actively being developed.
> I would propose this if there is an update.
> {quote}
> If this is generally agreeable, it seems straightforward to port the Sqoop
> 1.4.x based package from Bigtop 0.5 to trunk, perhaps as a new "sqoop1"
> package.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
