[ https://issues.apache.org/jira/browse/SQOOP-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186454#comment-14186454
]
Sqoop QA bot commented on SQOOP-1629:
-------------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12677538/SQOOP-1629.patch against branch
sqoop2.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} Patch compiled
{color:green}SUCCESS:{color} All tests passed
Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/473/console
This message is automatically generated.
> Sqoop2: Add unique constraint on the Config table for name and type
> -------------------------------------------------------------------
>
> Key: SQOOP-1629
> URL: https://issues.apache.org/jira/browse/SQOOP-1629
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.4
>
> Attachments: SQOOP-1629.patch, SQOOP-1629.patch, SQOOP-1629.patch
>
>
> this helps create top level config objects and use their names while creating the LINK
and JOB entities
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|