Currently we use {apachesolr_search_node} to track not only which nodes need to be updated, but also whether there were past attempts to delete a document (e.g. a deleted or unpublished node) which failed. This latter information become irrelevant if we delete the Solr index, so we shoudl rebuild this table fully to avoid making lots of extra irrelevant delete requests.

This is also important for development sites which may be doing bulk deletes of nodes - after such an operation deleting the index is likely to be more efficient than sending all those individual delete requests.

CommentFileSizeAuthor
#1 rebuild-table-509526-1.patch2 KBpwolanin

Comments

pwolanin’s picture

Title: {apachesolr_search_node} table shoudl be rebuilt when index is deleted » {apachesolr_search_node} table should be rebuilt when index is deleted
Status: Active » Needs review
StatusFileSize
new2 KB
anarchivist’s picture

+1 on this from me - this is one of the steps I added in my sample code to handle the batch reindexing process in #456420: Add Batch API support for rebuilding indexes.

pwolanin’s picture

Status: Needs review » Patch (to be ported)

committed to 6.x-1.x - needs to be ported to 6.x-2.x

pwolanin’s picture

Version: 6.x-1.x-dev » 6.x-2.x-dev
robertdouglass’s picture

Status: Patch (to be ported) » Fixed

fixed in 6.2

Status: Fixed » Closed (fixed)

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