airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2938) Change DB initialization in Registry server to use registry-refactoring code
Date Tue, 05 Feb 2019 18:57:00 GMT

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

ASF subversion and git services commented on AIRAVATA-2938:
-----------------------------------------------------------

Commit 94d4b8c984064bcc0a80d0cd39e96071a1e6b7d8 in airavata's branch refs/heads/develop from
Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=94d4b8c ]

AIRAVATA-2938 Fixing UNIQUE constraint


> Change DB initialization in Registry server to use registry-refactoring code
> ----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2938
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2938
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>         Attachments: app_catalog_diff.sql, credential_store_diff.sql, profile_service_diff.sql,
replica_catalog_diff.sql, sharing_catalog_diff.sql
>
>
> TODO
> * [x] Move DB intialization code to airavata-commons. Code in registry-core is duplicated
in airavata-sharing-registry-server and airavata-credential-store.
> ** Don't need a connection pool (JdbcStorage) for initializing a database
> ** Single DBInitializer class that takes a config object with JDBC properties etc.
> ** Each database has its own initialization class that can also have a postInit method
to do any database setup
> * [x] Update distribution bin assembly to include db scripts from registry-refactoring
> * [x] Update RegistryAPIServer to call DBInitializers from registry-refactoring
> * [x] code cleanup: DatabaseCreator copies
> ** (/) CredentialStoreInitUtil
> ** (/) orchestrator-core Initialize
> ** (/) registry-refactoring: expcatalog Initialize.java
> ** (/) registry-refactoring: replicacatalog Initialize.java
> ** (/) registry-refactoring: workflowcatalog Initialize.java
> ** -registry-core: appcatalog Initailize.java- registry-core is deprecated so no need
to convert these
> ** -registry-core: expcatalog Initialize.java-
> ** -registry-core: replicacatalog Initialize.java-
> ** (/) registry-server: appcatalog AppCatalogInitUtil
> ** (/) registry-server: DatabaseCreator
> ** (/) registry-server: ExpCatalogInitUtil
> ** (/) registry-server: ReplicaCatalogInitUtil
> ** (/) registry-server: WorkflowCatalogInitUtil
> ** (/) sharing-registry-server: JPAUtils
> ** (/) sharing-registry-server: Initialize
> ** -registry-tool: DBMigrator- not going to touch this now
> ** (/) gfac-service: Initialize
> * [x] code cleanup: DBInitializer copies
> ** (/) profile-service-commons: Utils.java
> ** (/) CredentialStoreInitiUtil
> ** -registry-core: Utils- registry-core is deprecated so no need to convert
> * [x] code cleanup: DerbyUtils.java copies
> ** AiravataDerbyServer
> ** other locations listed in above lists
> * [x] code cleanup: Merge DerbyUtils.java and DerbyDBManager.java
> * [x] run a DB schema diff between a clean database initialized by these refactored scripts
and a live existing Airavata develop database (dbdev.scigap.org)
> * [x] move Derby start code out of DBInitializer?
> * [x] Factor out EntityManagerFactory creation code from AppCatalogJPAUtils and use for
all databases
> * [x] turn off the feature in OpenJPA where it adds missing columns/tables automatically.
Instead we'll require DB scripts, migration scripts.
> * [ ] rerun DB schema diff after running migration scripts on live develop database



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message