You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Abraham Elmahrek (JIRA)" <ji...@apache.org> on 2015/02/08 21:34:34 UTC
[jira] [Updated] (SQOOP-1790) Sqoop2: Upgrade configs with name
conflicts
[ https://issues.apache.org/jira/browse/SQOOP-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abraham Elmahrek updated SQOOP-1790:
------------------------------------
Fix Version/s: (was: 1.99.5)
1.99.6
> Sqoop2: Upgrade configs with name conflicts
> -------------------------------------------
>
> Key: SQOOP-1790
> URL: https://issues.apache.org/jira/browse/SQOOP-1790
> Project: Sqoop
> Issue Type: Bug
> Components: sqoop2-server
> Affects Versions: 1.99.5
> Reporter: Abraham Elmahrek
> Assignee: Abraham Elmahrek
> Fix For: 1.99.6
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)