[
https://issues.apache.org/jira/browse/AIRAVATA-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15773290#comment-15773290
]
Anuj Bhandar commented on AIRAVATA-2291:
----------------------------------------
Upon discussing this issue with Airavata Team, I came across the following two
ways of handling this issue
* Develop an API level service (module), which calls the Registry API's of
two consecutive releases (Ex: 0.16 and 0.17), the module will then handle the
migration. Of-course, this solution is not the optimal one for obvious reasons
like, will have to change for each release, lots of dev work to accommodate the
huge number of registry api's.
* Generate sql delta scripts for migration, manual creation will take a lot
of time, hence using some open source tools to generate these scripts.
* Along with Delta scripts for current release migration, implement a
database Version Control for automating the creation of delta scripts for all
the releases.
I have created the sub-task for each one, Please feel free to comment and
suggest changes as necessary
> Database Migration Dev to Master
> --------------------------------
>
> Key: AIRAVATA-2291
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2291
> Project: Airavata
> Issue Type: New Feature
> Components: Airavata API, Registry API
> Affects Versions: 0.16, 0.17
> Reporter: Anuj Bhandar
> Assignee: Anuj Bhandar
> Labels: GATask
>
> As a part of Airavata 0.17 release the registry service has gone through
> major development and as result of this the development, database schema has
> been revamped.
> This is very common problem which almost all product based IT firms face
> atleast once in their application Dev life cycle, lets keep this Epic as a
> discussion place for developing a solution to address this issue in all
> future releases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
