activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "clebert suconic (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ARTEMIS-1653) Allow database tables to be created externally
Date Thu, 17 May 2018 02:43:09 GMT

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

clebert suconic closed ARTEMIS-1653.
------------------------------------
    Resolution: Fixed

> Allow database tables to be created externally
> ----------------------------------------------
>
>                 Key: ARTEMIS-1653
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1653
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Niels Lippke
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.6.0
>
>
> In some environments (e.g. production) it is not allowed that applications create their
own schema. It's common practice to pass DDL-Statetements to DBAs instead prior to rollout.
> Currently the broker does not support this scenario. If the required tables already exist
the broker fails to start.
> A better approach is that if the broker detects empy tables and initializes them in the
very same way it does if the tables dont't exist.
> See also discussion in [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html].



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

Mime
View raw message