sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1566) Sqoop2: Fix the upgrade logic for SQOOP-1498
Date Tue, 14 Oct 2014 03:39:34 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1566:

For the record, I've commited file {{SQOOP-1566-1.patch}} as that is the same that I've +1
on the review board. Please file and follow up JIRA if you need to alter it [~vybs].

> 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
>             Fix For: 1.99.4
>         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

View raw message