Bulk update handles "document_missing_in_index_exception"#392
Merged
jonavellecuerdo merged 1 commit intoJul 15, 2026
Merged
Conversation
ehanson8
approved these changes
Jul 15, 2026
jonavellecuerdo
deleted the
TIMX-642-bulk-update-handles-document-missing-in-index-exception
branch
July 15, 2026 15:10
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose and background context
This required update was identified in the process of investigating missing TIMDEX embeddings for
gismitandaspace. This fix addresses the missing embeddings forgismit. Please read the details in TIMX-642 for a summary of the issue.One might wonder--as I did 🤓 --the difference between the

document_missing_exceptionvsdocument_missing_in_indexexception. The screenshot in TIMX-642 showing thedocument_missing_in_indexexception was reindexing to AOSS (Serverless) and the screenshot below is reindexing to Cluster (Traditional):This suggests that the
document_missing_in_indexis specific to AOSS and it is an artifact of differing OpenSearch versions used by AOSS (Serverless) vs. Cluster (Traditional). While we are supporting two OpenSearch instances, we will need to handle both error types.How can a reviewer manually see the effects of these changes?
Screenshots in TIMX-642 and above for the
gismitexplain the issue.Includes new or updated dependencies?
NO
Changes expectations for external applications?
YES-ish: The TIMDEX dataset in Prod was synced to Dev on 2026-07-14 (yesterday). The TIMDEX dataset in Prod will still be missing embeddings for
gismitandaspaceuntil we regenerate embeddings as was done in Dev.What are the relevant tickets?
Code review