[
https://issues.apache.org/jira/browse/SQOOP-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636943#comment-13636943
]
Jarek Jarcec Cecho commented on SQOOP-994:
------------------------------------------
That's an excellent point, indeed it's not clearly visible what to do in this
case. As we're trying to guarantee that repository contain only properly
validated entries, I would personally thrown an exception and shut down Sqoop
server boot procedure. In this case user will be given option to either return
to old connector version or simply drop the connection/job object that is
causing upgrade issues. What do you think?
> Sqoop2: Upgrade: Add calling validation to the upgrade method
> -------------------------------------------------------------
>
> Key: SQOOP-994
> URL: https://issues.apache.org/jira/browse/SQOOP-994
> Project: Sqoop
> Issue Type: Sub-task
> Affects Versions: 1.99.2
> Reporter: Jarek Jarcec Cecho
>
> We should call connector's validator to see if the object case is good enough.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
