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

ASF subversion and git services commented on SQOOP-1566:
--------------------------------------------------------

Commit 6ae93e6ad846228bf56b8135ba83d1987c789dcf in sqoop's branch 
refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=6ae93e6 ]

SQOOP-1566: Sqoop2: Fix the upgrade logic for SQOOP-1498

(Veena Basavaraj via Jarek Jarcec Cecho)


> 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, SQOOP-1566-2.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)

Reply via email to