[SQOOP-1790] Sqoop2: Upgrade configs with name conflicts

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.99.5
• Fix Version/s: 1.99.6
• Component/s: sqoop2-server
• Assignee: Abraham Elmahrek
• Reporter: Abraham Elmahrek
• Created: 23/Nov/14 19:05
• Updated: 26/Feb/15 15:47
• Resolved: 26/Feb/15 15:10

Description

SQOOP-1636 added uniqueness on input names per type per config. For example, in 1.99.3, it was possible to have conflicting names in the Generic JDBC Connector:
https://github.com/apache/sqoop/blob/branch-1.99.3/connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/configuration/ImportTableForm.java#L29
https://github.com/apache/sqoop/blob/branch-1.99.3/connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/configuration/ExportTableForm.java#L29

Let's add migrations in the repository to handle this case.

Issue Links

• depends upon: SQOOP-2129 Sqoop2: SQ_SUBMISSION deletes should cascade
• relates to: SQOOP-1841 Sqoop2: Upgrade from 1.99.1 to 1.99.4 onwards is broken
• links to: Review board