community: Add support for order_by and canonical_filter fields in VertexAISearchRetriever #529
+57
−7
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.
PR Description
This PR introduces two new optional fields,
order_by
andcanonical_filter
, to theVertexAISearchRetriever
class. These fields enhance the flexibility and control over search queries when using Google Vertex AI Search.Type
🆕 New Feature
✅ Test
Issue
#530
Testing
I added the corresponding unit test for creating a search request to verify that the VertexAISearchRetriever correctly creates a
SearchRequest
object with the expected auto-populated fields, including the newly addedorder_by
andcanonical_filter
fields.Also, I tested it using my data in GCP, checking different configurations and verifying that the parameters are correctly applied and produce the expected results.
Thank you again Team!