When using Solr Search Integration, pressing the core search Re-index site button at /admin/settings/search also causes re-indexing of the Solr search index (and that is reflected at /admin/settings/apachesolr/index, which then says afterwards that:

 '0% of the site content has been sent to the server'.

I consider this an undesirable side-effect, and a "gotcha". It certainly caught me by surprise (and meant I had to repeat indexing of a large site over many days).

Where it is possible to have both core search and Solr search active, with the 2 systems apparently using different table, I insist it should be possible to separately trigger re-indexing of one system without affecting the other.

I am reporting this as a bug, although you might claim it is by-design. I could not find this behaviour documented, and certainly users should be warned, if possible in the user interface (which may be difficult to achieve in the core search settings page), or at least in the Solr Integration documentation (forgive me if it is there somewhere, otherwise do please add a very clear warning about this).

You might prefer to consider this a feature request, or better put, a request for redesign of the behaviour w.r.t. the existing core Re-index site button feature.

Comments

nick_vh’s picture

nick_vh
he/him
Location Ghent
commented

I don't think this will be fixed since this has been resolved in Drupal 7 and the search of Drupal 6 was never meant to be that sophisticated.
Unless you can supply us with a patch I think this will be a won't fix

pwolanin’s picture

pwolanin commented
Category: bug » support
Status: Active » Fixed

I agree with Nick - while the is a gotcha, it's the nature of integrating with the Durpal 6.x core search API completely.

When we open a 6.x-3.x branch, I'm certainly open to avoiding this problem.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.