You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2013/07/28 01:07:48 UTC
[jira] [Assigned] (BIGTOP-1016) Add a new package to bring back
Sqoop 1.4.x
[ https://issues.apache.org/jira/browse/BIGTOP-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik reassigned BIGTOP-1016:
------------------------------------------
Assignee: Sean Mackrory
> 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
> Assignee: Sean Mackrory
> Labels: hackathon-7-2013
>
> 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