You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Boglarka Egyed (JIRA)" <ji...@apache.org> on 2017/08/10 14:18:00 UTC

[jira] [Updated] (SQOOP-3007) Sqoop2: Improve repository upgrade mechanism

     [ https://issues.apache.org/jira/browse/SQOOP-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Boglarka Egyed updated SQOOP-3007:
----------------------------------
    Labels: features  (was: features newbie)

> Sqoop2: Improve repository upgrade mechanism
> --------------------------------------------
>
>                 Key: SQOOP-3007
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3007
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-derby-repository, sqoop2-postgresql-repository
>    Affects Versions: 1.99.7
>            Reporter: Boglarka Egyed
>              Labels: features
>
> Repository upgrade mechanism should be improved to support moving from a release build of Sqoop2 to a cut of the sqoop2 (master) branch if a user needs some upstream feature and then wants to switch back to release in the future. This should provide a proper repository upgrading work throughout the whole process so the user doesn't have to wait for the next release of Sqoop2 to fix a bug.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)