[
https://issues.apache.org/jira/browse/SQOOP-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177062#comment-14177062
]
Qian Xu commented on SQOOP-1593:
--------------------------------
The configuration upgrader is able to upgrade config from previous state, but
will fail to upgrade from an even earlier state. In other words, there is no
tracking mechanism for configuration changes, right? I think in early
development stage, fast-fail is okay. But for a product grade release, a good
version tracking mechanism is required.
> If connector registration is failed, the sqoop2 server cannot startup
> ---------------------------------------------------------------------
>
> Key: SQOOP-1593
> URL: https://issues.apache.org/jira/browse/SQOOP-1593
> Project: Sqoop
> Issue Type: Bug
> Components: connectors
> Affects Versions: 2.0.0
> Reporter: Qian Xu
>
> I noticed that if a connector is failed to registrered (e.g. in case
> configuration upgrade failed), the sqoop2 server will NOT startup. My
> expected behaviors would be disable affected connector(s) link(s) and job(s),
> but server should be able to startup. Is the behavior expected by design?
> {code}
> 2014-10-20 14:15:14,683 ERROR core.SqoopServer
> [org.apache.sqoop.core.SqoopServer.initialize(SqoopServer.java:56)] Server
> startup failure
> org.apache.sqoop.common.SqoopException: CONN_0007:Connector registration
> failed
> at
> org.apache.sqoop.connector.ConnectorManager.registerConnectors(ConnectorManager.java:206)
> at
> org.apache.sqoop.connector.ConnectorManager.initialize(ConnectorManager.java:167)
> at org.apache.sqoop.connector.ConnectorManager.initialize(ConnectorMan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
