sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boglarka Egyed (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3007) Sqoop2: Improve repository upgrade mechanism
Date Thu, 29 Sep 2016 18:32:20 GMT

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

Boglarka Egyed commented on SQOOP-3007:
---------------------------------------

Hi All,

A couple of questions have turned up during the design phase and I would like to involve the
whole community to discuss them.

Considerable changes would be:

1.)  Storing the upgrade SQL statements in separate sql-files. I think the benefits would
be:
- Separate upgrade statements for upgrading logic
- Encapsulates upgrade steps more explicitly
- Easier versioning of the files
- Quick manual testing opportunity
- Easier to test just the upgrades, you don't need to run the whole code just the statements
- Order of the statements is explicitly encoded in the sql-file, we wouldn't need to worry
about ordering the steps
- Changes wouldn't require a whole build process


2.) Adding a capability for rollback functionality too. Needed in case of for example DDLs.

Every opinion, suggestion, concern would be more than welcome on these two questions.

Thank you,
[~BoglarkaEgyed]

> Sqoop2: Improve repository upgrade mechanism
> --------------------------------------------
>
>                 Key: SQOOP-3007
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3007
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-derby-repository, sqoop2-postgresql-repository
>    Affects Versions: 1.99.7
>            Reporter: Boglarka Egyed
>            Assignee: Boglarka Egyed
>              Labels: features, newbie
>
> Repository upgrade mechanism should be improved to support moving from a release build
of Sqoop2 to a cut of the sqoop2 (master) branch if a user needs some upstream feature and
then wants to switch back to release in the future. This should provide a proper repository
upgrading work throughout the whole process so the user doesn't have to wait for the next
release of Sqoop2 to fix a bug.



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

Mime
View raw message