YARPP working with InnoDB

Yes! That’s what YARPP does if you run it with wp_posts in InnoDB. It’ll first warn you about it, and tell you that it can’t create a fulltext index, but then it’ll simply work by just looking at taxonomies. You may need to lower the match threshold, though.

With fulltext support in mysql 5.6.4+ with innodb, will yarpp take advantage of that?

Yes, hopefully, though MySQL 5.6+ adoption is going to take a long time. People are slow to switch…

Are you running InnoDB with fulltext right now?

Hi Mitcho ??

Yes, it is warning us about it – and it doesn’t seem to work…?

Here’s an example: https://uk.iacworld.org/get-vibrational-state-astral-projection/

There are a couple of articles on the very same topic (very similar) but nothing comes up under related posts.

I lowered the maximum display of related posts to 1; not sure if that’s what you mean by lowering the match threshold…

Any help at this point very much appreciated.

Thanks in advance!!

@patrilux: are you having the same issue with InnoDB tables? Or is this a different issue?

See a longer post on InnoDB vs MyISAM tables here: https://www.ads-software.com/support/topic/yarpp-requires-your-posts-table-to-use-the-myisam-storage-engine?replies=2#post-3959160

@mitcho

Any update on MySQL 5.6’s FULLTEXT support for InnoDB?

We have already switched to MySQL 5.6 and InnoDB.

Another request here… huge traffic and a noticeable improvement in db response time when we change the format of the posts table from MyISAM to InnoDB. Now that 5.6 supports it, can you pleas let YARPP support full functionality with InnoDB posts tables?

Indeed that feature would be nice (just joining the request pool).

+1