Hi Anuj, Thank you. I have a better understanding of the problem now. I have another question. Can you let me know how Airavata is managing this problem now? I know that it's done manually. But is there any particular way by which you are tackling it now?
Regards, Sneha Tilak Regards, *Sneha Tilak* On Sun, Apr 2, 2017 at 2:17 PM, Anuj Bhandar <[email protected]> wrote: > Hello Sneha, > > Here are the Airavata ER Diagram you have been looking for : > https://issues.apache.org/jira/browse/AIRAVATA-2098 > > I appreciate that you have been looking at these to come up with better > solution, here are some of the main problem as stated by Suresh during the > Adv Science Gateway class: > > - How will be the branching strategy considering there are different > versions of DB schema in most of the branches, Can Liquibase have a central > repository to store DB changes, just like github.com is for GIT > - How well the LiquiBase directly bolts on to ORM layers like > Hibernate and Open JPA to capture changes in database > - Though you have already explained this bit in the class, But how > will the Liquibase handle Code merges from different branches, for example > : There are two branches, master and develop, both will have there own > version of changelog file, what happens when we merge these two branches. > - Does Liquibase has good support for Maven integration ? > > Thanks and best regards, > Anuj Bhandar > > On 04/02/2017 01:42 PM, Suresh Marru wrote: > > Hi Sneha, > > Here are some database schema’s which should get you a sense of the > catalog’s - https://github.com/apache/airavata/tree/master/modules/ > registry/registry-core/src/main/resources > > For the proposal, you can propose how you generally want to approach the > problem and factor in time for learning Airavata specific schemas. > > Suresh > > On Apr 2, 2017, at 12:46 AM, Sneha Tilak <[email protected]> wrote: > > Hi Suresh, dev > > Thank you for the links. I went through the threads. I will look into the > Liquibase approach that Anuj suggested. > I would like to know more about the Airavata database schema in order to > propose a confined solution. Is there any place where I can look it, Anuj? > > Regards, > Sneha Tilak > > > Regards, > *Sneha Tilak* > > On Sat, Apr 1, 2017 at 11:51 PM, Suresh Marru <[email protected]> wrote: > >> Hi Sneha, >> >> This is an open problem for Airavata and we will be interested in what >> you plan to propose. Here are some threads on this topic: >> >> https://issues.apache.org/jira/browse/AIRAVATA-2291 >> >> http://www.mail-archive.com/[email protected]/msg11325.html >> >> Anuj mentioned he attached some ER diagrams of database schemas, you may >> want to search for them in JIRA. Anuj? >> >> Let us know if you have specific questions. >> >> Suresh >> >> On Apr 1, 2017, at 6:39 PM, Sneha Tilak <[email protected]> wrote: >> >> Hello dev, >> >> I am interested in participating in the Google Summer of Code '17. The >> proposal below is what I would like to work on - >> >> Title: Database Versioning in Apache Airavata. >> >> Problem Statement: Considering Airavata, which has multiple developers >> contributing to the project, there is bound to be a situation where the >> databases and the data stored in it are not synchronized. Even with a >> single instance, it takes a significant amount of time to make sure that >> the changes are in sync when more than one developer works on it. The goal >> of this project is to introduce versioning of databases (schema and data) >> when merging a developed branch to the master branch before deploying the >> revision. >> >> I would love to hear your suggestions regarding the same. >> >> Regards, >> Sneha Tilak >> >> >> > > >
