[jira] [Commented] (SQOOP-1790) Sqoop2: Upgrade configs with name conflicts

["Sqoop QA bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SQOOP-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14335808#comment-14335808 ] 

Sqoop QA bot commented on SQOOP-1790:
-------------------------------------

Testing file [SQOOP-1790.0.patch|https://issues.apache.org/jira/secure/attachment/12700634/SQOOP-1790.0.patch] against branch sqoop2 took 0:00:10.280136.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
{code}error: cannot apply binary patch to 'test/src/test/resources/repository/derby/derby-repository-1.99.3.tar.gz' without full index line
error: test/src/test/resources/repository/derby/derby-repository-1.99.3.tar.gz: patch does not apply
{code}

{color:green}SUCCESS:{color} Clean was successful

Console output is available [here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1093/console].

This message is automatically generated.

> 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
>            Priority: Blocker
>             Fix For: 1.99.6
>
>         Attachments: SQOOP-1790.0.patch
>
>
> 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)