Add Retries & Fallback to SQL Retriever #10341
Merged
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.
Description
LLMs will not always generate correct SQL queries to be used with
pgvector
for hybrid search. In this case, we should try to correct the queryn
times, and then fallback to our default retriever if executing the corrected queries still return errors.This way, worst case, we just use our default retriever without metadata instead of returning an error.
Related to ML-240
Type of change
Verification Process
To ensure the changes are working as expected:
./tests/unit/test_sql_retriever.py
Additional Media:
Checklist: