I am trying to perform scripted updates to a node (as part of a workflow, not a one-time thing), but due to both the frequency of updates and amount of content I want to avoid re-indexing the node every time there is an update. I have looked, but so far haven't found a way to save a node and instruct Solr/Drupal to not send the node for re-indexing (I am not trying to exclude all updates, nor all nodes of a specific content type).

Comments

orbmantell created an issue. See original summary.

pwolanin’s picture

Status: Active » Fixed

Simply executing a node_save() won't send the new node to the Solr index unless you have some other module in place. It only indexes content on cron.

jgrubb’s picture

Status: Fixed » Closed (works as designed)

If I'm reading this correctly, this just sounds too complicated to implement here with too small a user base.