[
https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740528#action_12740528
]
Sébastien Launay commented on JCR-1435:
---------------------------------------
This will work but you need to duplicate the mysql.ddl and therefore maintain
it on your own, even if there is a small chance it will change over time
because it will imply a migration process.
Another thing is that the default table engine is often MyISAM and this engine
is not supported in a cluster config.
Indeed, there will be no RDBMS locking involved when accessing the journal
table and data integrity will not be enforced.
> 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.
