[
https://issues.apache.org/jira/browse/SQOOP-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14233843#comment-14233843
]
Qian Xu edited comment on SQOOP-1812 at 12/4/14 4:49 AM:
---------------------------------------------------------
I've changed the patch by adding a check of repository version. I've also
provide a test case for that. I hope committers can approve this patch asap,
because sqoop2 server cannot restart in real world for already couple of weeks.
[~vybs] Yes. I think upgrade path should have a higher test coverage.
was (Author: stanleyxu2005):
I added a check of repository version instead of increasing repository version
in previous patch. It will be easier and cleaner to refactor integration tests
without breaking too many things.
> 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.2.patch, SQOOP-1812.3.patch,
> SQOOP-1812.4.patch, SQOOP-1812.5.patch, 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)
