MySQL NDBcluster engine

Permalink
We run a popular web service and are evaluating concrete5 for our front end web site. The install went great for the most part, but we use a high availability mysql setup. All HA mysql setups require that each table be of engine type "ndbcluster".

All concrete5 tables are set with engine of MyIsam which is pretty common, however there are some things that are done with the indexes on the tables that makes porting the tables from myisam to ndbcluster problematic.

Specifically, ndbcluster does not support fulltext indexes, so the search functionality looks like it will be degraded on an ha setup.

Not sure what the best solution is really but thought ya'll might like to know.

 
PortlandLabs replied on at Permalink Reply
PortlandLabs
This actually probably won't affect concrete5 in 5.4.1.1. While we do have a fulltext index, our search block by default just does a relatively simple "like"-based search (rather than using the fulltext index.) You can still use the fulltext index in your custom queries (if you extend the PageList class) or if you're using the "search index" field in the dashboard page search index, but as far as public facing blocks are concerned, I don't think fulltext does too much by default any longer.