Wait for vector index to stabilize - #70649
Open
o-nikolas wants to merge 1 commit into
Open
Conversation
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.
The Bedrock retrieve-and-generate system test creates an OpenSearch
Serverless vector index and then immediately proceeds to Bedrock
Knowledge Base ingestion. However, an acknowledged index-creation call
does not guarantee the index is ready for use: OpenSearch Serverless
materializes the index asynchronously and exposes no status API to
check on its progress. When ingestion starts before the index can
serve requests, the test fails intermittently.
Since there is no status API for the index, this change polls a
trivial
match_allsearch against the new index as a readiness probe(retrying
TransportErrorup to 30 times at 5-second intervals)before allowing downstream tasks to run, eliminating the race.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.