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/13 22:09:35 UTC

[jira] [Commented] (SQOOP-1566) Sqoop2: Fix the upgrade logic for SQOOP-1498

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

Veena Basavaraj commented on SQOOP-1566:
----------------------------------------

the latest patch uploaded has the changes for the upgrade logic for sqoop-1498 DB changes. I have also added a few comments explaining how upgrade works and what it really means.

> Sqoop2: Fix the upgrade logic for SQOOP-1498
> --------------------------------------------
>
>                 Key: SQOOP-1566
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1566
>             Project: Sqoop
>          Issue Type: Improvement
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>         Attachments: SQOOP-1566-1.patch
>
>
>  fix the upgrade logic for 1498 changes.
> While fixing the upgrade logic, added comments on how the upgrade logic works.
> -renamed test methods to reflect what they are upgrading and what they are infact testing. 
> -renamed the internals to exactly mean "schema" upgrades, since we only allow/ do scheme upgrades the repository
> -Also updated the names on the repository api to clearly state the difference between upgrade and update operations on connector / driver.



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