User warning after turning on 'Include content fields in matching' [#1261050]

I got this error after enabling 'Include content fields in matching' under views arguments.

user warning: Can't find FULLTEXT index matching the column list query: SELECT node.nid AS nid, MATCH (node_revisions.body, node_revisions.title) AGAINST ('Free Shipping on Under The Nile Organic Baby Clothes & Toys!') OR MATCH (content_type_company_profile.field_products_services_value, content_type_company_profile.field_services_value) AGAINST ('Free Shipping on Under The Nile Organic Baby Clothes & Toys!') OR MATCH (content_type_deal.field_description_value, content_type_deal.field_description_format, content_type_deal.field_deal_restrictions_value, content_type_deal.field_deal_restrictions_format) AGAINST ('Free Shipping on Under The Nile Organic Baby Clothes & Toys!') OR MATCH (content_type_product.field_review_value, content_type_product.field_review_format, content_type_product.field_pros_value, content_type_product.field_cons_value) AGAINST ('Free Shipping on Under The Nile Organic Baby Clothes & Toys!') AS score, node.title AS node_title, node.type AS node_type, COUNT(node.nid) AS node_count FROM node node LEFT JOIN node_revisions node_revisions ON node.vid = node_revisions.vid LEFT JOIN content_type_company_profile content_type_company_profile ON node.vid = content_type_company_profile.vid LEFT JOIN content_type_deal content_type_deal ON node.vid = content_type_deal.vid LEFT JOIN content_type_product content_type_product ON node.vid = content_type_product.vid WHERE (node.moderate = 0) AND (node.status <> 0) AND (node_revisions.nid <> 4901) GROUP BY nid, score, node_title, node_type HAVING score > 1 ORDER BY score DESC LIMIT 0, 5 in /public_html/sites/all/modules/views/includes/view.inc on line 771.

Comments

Comment #1

jordojuice CreditAttribution: jordojuice commented 27 August 2011 at 00:27

Try running cron. It should reset indexes during cron if they're inaccurate in the query. It was designed so indexes are updated during cron if they're inaccurate like this, but I'll definitely be looking deeper into this again because obviously this shouldn't happen.

EDIT: I reproduced this and it was fixed by running cron, but the matches don't seem accurate. It is properly indexing the CCK tables/columns during cron, but the query built to include CCK fields I think needs work. I'll be working on this tonight because there should not have been errors in the first place.

Comment #2

Janner CreditAttribution: Janner commented 27 December 2011 at 15:36

I'm getting exactly the same error as posted above, but running cron does not fix the problem.

Any suggestions?

Comment #3

jordojuice CreditAttribution: jordojuice commented 18 February 2012 at 01:47

I've done a lot of work on both Views integrated branches, but I think this is the only issue I haven't debugged. I'll be getting to it tonight, though, and hopefully will have it fixed before another release.

Comment #4

jordojuice CreditAttribution: jordojuice commented 20 February 2012 at 08:25

Status:

Active

» Postponed (maintainer needs more info)

Alright. I did some work on how columns are indexed particularly in the 6.x-2.x branch, so what I need to know is whether this error is still occurring. Until then I am unable to reproduce the error. The only situation in which I've run into this is when something goes wrong during installation that causes the initial indexing of the node_revisions table to fail.