Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.99.7
-
None
Description
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.