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

ASF GitHub Bot commented on ARTEMIS-1653:
-----------------------------------------

GitHub user franz1981 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/2028

     ARTEMIS-1653 Allow database tables to be created externally

    https://issues.apache.org/jira/browse/ARTEMIS-1653

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/franz1981/activemq-artemis 1.x_ARTEMIS-1653

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/2028.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2028
    
----
commit 24f7caba501c102fcc88d41926ab9d7aefc3e315
Author: Niels Lippke <nlippke@...>
Date:   2018-01-28T16:53:35Z

    ARTEMIS-1653 Allow database tables to be created externally
    
    (cherry picked from commit eab498456762c3df0f786b1f9ae4e372fdbbfa32)

commit e10391dc885dd74b404d41f04c76d163f1c8227d
Author: Francesco Nigro <nigro.fra@...>
Date:   2018-04-03T08:11:04Z

    ARTEMIS-1653 Allow database tables to be created externally
    
    (cherry picked from commit c7651853cdb291dfa3bd2906e1e082fd06cff612)

----


> 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)

Reply via email to