Fix DRIFT search on Azure AI Search #1645
Merged
Conversation
This file contains 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
AlonsoGuevara
previously approved these changes
Jan 21, 2025
|
Edit: removed the new DRIFT smoke test because it is brittle. We will address that in a separate PR to unblock patching DRIFT with this bugfix. |
AlonsoGuevara
approved these changes
Jan 21, 2025
3 tasks
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.
AZAIS embeddings were not including the vector itself in the list of retrievable fields, which DRIFT relies on for local cosine similarity checks.
This also adds DRIFT and Basic search queries to the smoke tests, so we should catch search issues more reliably with AZAIS and lancedb.