You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Sébastien Launay (JIRA)" <ji...@apache.org> on 2008/04/28 12:08:57 UTC
[jira] Updated: (JCR-1435) Choose the MySQL engine for database
storage (default to MyISAM)
[ https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sébastien Launay updated JCR-1435:
----------------------------------
Attachment: jackrabbit-1.4.x-mysql-engine-2008-04-28.patch
jackrabbit-trunk-mysql-engine-2008-04-28.patch
Update of patches with the following modification:
* move mysqlEngine property from BundleFsPersistenceManager to MySqlPersistenceManager
> Choose the MySQL engine for database storage (default to MyISAM)
> ----------------------------------------------------------------
>
> Key: JCR-1435
> URL: https://issues.apache.org/jira/browse/JCR-1435
> Project: Jackrabbit
> 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.