sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sqoop QA bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1636) Sqoop2: Add unique constraint to the SQI_INPUT name per config per configurable
Date Wed, 29 Oct 2014 04:55:34 GMT

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

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

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12677820/SQOOP-1636.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/485/console

This message is automatically generated.

> Sqoop2: Add unique constraint to the SQI_INPUT name per config per configurable
> -------------------------------------------------------------------------------
>
>                 Key: SQOOP-1636
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1636
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 2.0.0
>
>         Attachments: SQOOP-1636.patch
>
>
> the input names across A config for a configurable should be unique.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message