jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sébastien Launay (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-1435) Choose the MySQL engine for database storage (default to MyISAM)
Date Fri, 07 Aug 2009 13:10:14 GMT

    [ https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740541#action_12740541
] 

Sébastien Launay commented on JCR-1435:
---------------------------------------

> OTOH, IIUC with the proposed patch it's not possible anymore to implicitly use the default
engine, e.g. overriden in my.cnf.
That's right but the patch can be adapted to use the default engine and use "engine=${mysqlEngine}"
only when engine property is set.

> in which case you'd have to specify a different engine in my.cnf.
This is a solution but i prefer to choose the engine when declaring the PersistenceManager
(because i may want to use the different default engine everywhere else or i simply do not
have the admin privilege to change this setting in my.cnf).

> Choose the MySQL engine for database storage (default to MyISAM)
> ----------------------------------------------------------------
>
>                 Key: JCR-1435
>                 URL: https://issues.apache.org/jira/browse/JCR-1435
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.1
>         Environment: MySQL with NDB Cluster engine
>            Reporter: Sébastien Launay
>         Attachments: jackrabbit-1.4.x-mysql-engine-2008-04-28.patch, jackrabbit-1.4.x-mysql-engine.patch,
jackrabbit-trunk-mysql-engine-2008-04-28.patch, jackrabbit-trunk-mysql-engine.patch
>
>
> The MySQL scripts embedded into Jackrabbit does not specify the engine to use.
> So by default MyISAM is used and we cannot change this.
> But, depending on the environment we may want to use an alternate engine like
> InnoDB (for transaction support) or in my case NDB Cluster (for high availability).
> We can still manually created the tables and then set the wanted engine, but it would
> be better if there was a parameter for the engine for component in the repository.xml
> for automatic table creation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message