When a taxonomy changes, or a new taxonomy is applied to a content type, a re-indexing is needed or else the expected search results don't appear. Maybe this is a second example of the use case I describe here for a "Developers" fieldset on the performance page.

Consider a radio button for "Re-index on taxonomy change (instead of waiting for cron*)" plus a message that this is being done. If there's no use case where developers start out with a small set of content and a taxonomy they're experimenting with, then maybe this is a bad idea.

NOTE * Or for all I know, this is a job for supercron. Another dependency...

Comments

cpliakas’s picture

cpliakas commented
Status: Active » Closed (won't fix)

Hi shunting.

After spending some time thinking about this, I think it may be outside of the scope of Search Lucene API core. However, it is a very cool idea and might be a great contrib as more people are starting to use the Search Lucene API module suite. I am respectfully marking this as "won't fix", but I do hope that the idea is realized in a contributed module sometime soon.

Thanks again for the great ideas,
Chris

cpliakas’s picture

cpliakas commented

Task #612264: Implement the batch API to allow admins to rebuild the entire index without having to run cron might be another approach to satisfy the desired behavior. Although rebuilds won't happen automatically, there will be an option in the admin interface to rebuild the index in one shot without having to run cron.