Solr4 Entites Not Being Removed with deleteByQuery

I'm noticing the same problem. None of my nodes are getting removed.

Changing priority to major. Pretty big bug.

Here's a hack patch to resolve the issue.

If you need to fix your install, you might want to look at my module to prune non-existant nodes from a solr index (with out having to delete the whole thing).

#885484: "Delete Orphaned Nodes from Index" - a batch API for large sites

I'll look at this as soon as possible, Might need to add some tests so we can actually figure this out. Too bad the testbot does not have a solr running ;-)

We are running this one against a solr4 server and can confirm that the patch in #3 works for deleting nodes.

Is this only a problem with solr 4?

Is this only a problem with solr 4?

Solving this another way until we've figured it out. Omitting the delete by query is not an option afaik.

Committed the following patch and will do a follow-up asap

This patch actually solves multiple Solr 4 problems that we currently encounter. For some reason it is way stricter when sending documents so we should figure that out.

Oeps, my bad

#12: 1874420-11.patch queued for re-testing.

DummySolr did not have the getSolrVersion method

late night coding makes up for a whole lot of errors, and my simpletest is broken so relying on drupal.org...

Looking for a more root cause to this problem

https://issues.apache.org/jira/browse/SOLR-3432

Ok, so it seems that the id slashes trigger a regular expression in Solr 4.0 and that is why the query did not work. This patch should solve it without working around it.

Committed to 7.x-1.x.

Is the patch backported to latest 6.x-3.x-dev(Straight backport of the 7.x-1.x branch) as well ?

waiting for 6.3 support

+++ b/apachesolr.api.phpundefined
@@ -232,13 +232,13 @@ function hook_apachesolr_delete_by_query_alter($query) {
+function hook_apachesolr_exclude($entity_id, $entity_type, $row, $env_id) {

+++ b/apachesolr.index.incundefined
@@ -972,7 +972,7 @@ function apachesolr_term_reference_indexing_callback($node, $field_name, $index_
@@ -987,10 +987,14 @@ function apachesolr_term_reference_indexing_callback($node, $field_name, $index_

@@ -987,10 +987,14 @@ function apachesolr_term_reference_indexing_callback($node, $field_name, $index_
         // regardless of whether the facet is set to show as a hierarchy or not.
         // We would need a separate field if we were to index terms without any
         // hierarchy at all.
-        $fields[] = array(
-          'key' => $index_key,
-          'value' => $ancestor->tid,
-        );
+        // If the term is singular, then we cannot add another value to the
+        // document as the field is single
+        if ($field_info['multiple'] == true) {
+          $fields[] = array(
+            'key' => $index_key,
+            'value' => $ancestor->tid,
+          );

seems this slipped in the patch. Some explanation here : If the index_key is single and the field is single, there is no point in having multiple values in the field causing solr to break. It slipped in this patch so it's worth to mention what was done here.

// Index parent term against the field. Note that this happens
        // regardless of whether the facet is set to show as a hierarchy or not.
        // We would need a separate field if we were to index terms without any
        // hierarchy at all.
        // If the term is singular, then we cannot add another value to the
        // document as the field is single
        if ($field_info['multiple'] == true) {
          $fields[] = array(
            'key' => $index_key,
            'value' => $ancestor->tid,
          );
        }

The code that slipped in actually caused big problems: #1984664: Single-valued taxonomy field facets disappear after upgrading from 7.x-1.1

That's because the $ancestors variable doesn't just contain the term's parents; it contains the term itself also. So single-valued taxonomy fields are no longer being indexed.

I have a patch to fix it in the above issue.

Actually, even beyond that problem, the $field_info['multiple'] == true check doesn't really make sense to me here for other reasons; see my comment at #1984664-12: Single-valued taxonomy field facets disappear after upgrading from 7.x-1.1 for why.