[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16415715#comment-16415715 ]
ASF subversion and git services commented on ARTEMIS-1653: ---------------------------------------------------------- Commit b95afbf9363ad57a5c4a0a744220514d2d753908 in activemq-artemis's branch refs/heads/master from [~nlippke] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=b95afbf ] ARTEMIS-1653 Allow database tables to be created externally In some environments it is not allowed to create a schema by the application itself. With this change the AbstractJDBCDriver now tests if an existing table is empty and executes further statements in the same way as if the table does not exist. > 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 > Priority: Major > > 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)