Product fails to index due to incorrect use of partial update flag – Lucidworks

Issue

Some documents fail to index because the Solr partial update indexer stage is executed instead of the full Solr indexer. This behavior occurs even when the documents do not yet exist in Solr and thus should be added rather than updated.

Diagnosis

Fusion logs show repeated failures during indexing, including the following message:

IndexStageException: Cannot retrieve (empty or invalid queryResponse) the document identified

This error typically occurs when a flag used as a conditional for the Partial Indexer stage is evaluated to true, indicating that only a partial update should be performed. However, if the document does not yet exist in Solr, the partial update will be rejected if the Reject Update if Solr Document Not Present option is selected.

Environment

Fusion 5 and above.

Cause

If Reject Update if Solr Document Not Present is selected, this is expected behavior if a new document is sent through this pipeline stage.

If the partial stage is executed based on conditional logic, the condition being checked may be getting set to true inappropriately.

Resolution

Review the Solr Partial Indexer stage configuration.

Steps to resolve

Locate the index pipeline used for the job experiencing indexing failures.
Identify the Partial Solr Indexer stages and determine if it has a customized condition.
- If it is unconditional, then ensure Reject Update if Solr Document Not Present is disabled if that option is not desired.
- If it is conditional, verify that any logic that affects how the condition is valuated is operating correctly.

Example correction, where the context variable "partial" is used for the execution of the Partial indexer stage.

if (documentExistsInSolr(ctx.get("docId"))) {
ctx.put("partial", true);
} else {
ctx.put("partial", false);
}

Replace documentExistsInSolr with appropriate logic or use an upstream stage to check Solr for document presence.