[
https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440542#comment-16440542
]
ASF GitHub Bot commented on ARTEMIS-1653:
-----------------------------------------
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/1997
+1 Franz.
On Tue, 17 Apr 2018, 07:27 nlippke, <[email protected]> wrote:
> @franz1981 <https://github.com/franz1981> I totally agree. Broker should
> not run any DDL-Statements if tables are managed by a DBA.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/activemq-artemis/pull/1997#issuecomment-381861933>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AAOCy20Z6HWeWC2cCB2yTAh1OstwXlDeks5tpYtjgaJpZM4TKJau>
> .
>
> 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.5.1
>
>
> 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)
