You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/10/23 03:17:33 UTC

[jira] [Commented] (SQOOP-1569) SQOOP2: Preserve old job/link configuration when upgrading connectors

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

Veena Basavaraj commented on SQOOP-1569:
----------------------------------------

+ 1

> SQOOP2: Preserve old job/link configuration when upgrading connectors
> ---------------------------------------------------------------------
>
>                 Key: SQOOP-1569
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1569
>             Project: Sqoop
>          Issue Type: Improvement
>            Reporter: Gwen Shapira
>
> Right now the connector upgrade code can overwrite the existing configuration of jobs/links.
> This can lead to behavior that is surprising to users (you don't necessarily think of backing up the repository when dumping a new connector jar) and difficult to debug.
> I suggest automatically storing (and time-stamping) the previous versions.
> This should be completely transparent to the upgrade code and also to anyone accessing the configurations (they should always just get the latest version). 
> The design I have in mind is of slowly changing dimension. Types 2, 4 or 6 will work. Possibly with a view to hide the new behavior from the rest of the code-base.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)