You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2013/04/19 07:49:17 UTC

[jira] [Commented] (SQOOP-994) Sqoop2: Upgrade: Add calling validation to the upgrade method

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

Hari Shreedharan commented on SQOOP-994:
----------------------------------------

This is an interesting problem. It is easy enough to call the validate methods, but the question is how to handle a validation failure? Since the new connector may not work with older metadata for connections and jobs, rolling back the metadata upgrade is not likely to be good enough. We can somehow mark the connections and jobs as invalid and make sure the user (and later if the user is an admin) sees it when they login. But that is only error reporting, recovery may not even be possible.
                
> 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