You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Sqoop QA bot (JIRA)" <ji...@apache.org> on 2014/11/26 04:05:12 UTC

[jira] [Commented] (SQOOP-1812) Sqoop2: Repository upgrade issue will prevent server startup

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

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

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

This message is automatically generated.

> Sqoop2: Repository upgrade issue will prevent server startup
> ------------------------------------------------------------
>
>                 Key: SQOOP-1812
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1812
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Qian Xu
>            Assignee: Qian Xu
>            Priority: Blocker
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1812.patch
>
>
> Sqoop2 server will be killed silently shortly. The root cause is that sqoop2 server tries to add an existing constraint repeatedly.
> Here are the steps to reproduce:
> 1. Deploy newly built sqoop2 binary
> 2. Start sqoop2 server (and just wait for server startup complete)
> 3. Stop the server and restart the server



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