activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1653) Allow database tables to be created externally
Date Tue, 17 Apr 2018 06:22:00 GMT


ASF GitHub Bot commented on ARTEMIS-1653:

Github user franz1981 commented on the issue:
    @nlippke @mtaylor I have updated this PR to avoid issues with concurrent creations of
tables/indexes for the JDBC Journal with Oracle (there is a test attached): when a table seems
to exists both CREATE TABLE and CREATE INDEX statements are no longer used to initialize it.
    That is useful to allow a shared store to concurrently start 2 journals on the same database
and while rebooting the broker with an empty journal (table already existent, but empty ie
no need to create index twice).
    That means that a DBA should take care to create table and indexes (if any), but if it
will just create tables, the broker won't create any index on them, wdyt?

> Allow database tables to be created externally
> ----------------------------------------------
>                 Key: ARTEMIS-1653
>                 URL:
>             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|].

This message was sent by Atlassian JIRA

View raw message