You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2019/03/21 03:02:00 UTC

[jira] [Closed] (AIRAVATA-2291) Database Migration Dev to Master

     [ https://issues.apache.org/jira/browse/AIRAVATA-2291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru closed AIRAVATA-2291.
----------------------------------
    Resolution: Fixed

Closing the epic as the migration scripts are working now

> 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
>            Priority: Major
>              Labels: GATask
>             Fix For: 0.17
>
>
> 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
(v7.6.3#76005)