[
https://issues.apache.org/jira/browse/SQOOP-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225802#comment-14225802
]
Veena Basavaraj commented on SQOOP-1812:
----------------------------------------
Good catch, I was hoping we dont even enter this code path and invoke
createOrUpgrade if the current repo version is same as the latest version. But
if we dont guard that then it makes sense why this happens.
Hence I felt that we shud have test to not even invoke this method. But your
fix is also good
> 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)
