-
Notifications
You must be signed in to change notification settings - Fork 163
chore: support for pre-filters in $vectorSearch MCP-240 #689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -47,7 +47,7 @@ const VectorSearchStage = z.object({ | |
| filter: zEJSON() | ||
| .optional() | ||
| .describe( | ||
| "MQL filter that can only use pre-filter fields from the index definition. Note to LLM: If unsure, use the `collection-indexes` tool to learn which fields can be used for pre-filtering." | ||
| "MQL filter that can only use filter fields from the index definition. Note to LLM: If unsure, use the `collection-indexes` tool to learn which fields can be used for filtering." | ||
| ), | ||
| embeddingParameters: zSupportedEmbeddingParameters | ||
| .optional() | ||
|
|
@@ -59,11 +59,21 @@ const VectorSearchStage = z.object({ | |
| }); | ||
|
|
||
| export const AggregateArgs = { | ||
| pipeline: z | ||
| .array(z.union([AnyStage, VectorSearchStage])) | ||
| .describe( | ||
| "An array of aggregation stages to execute. $vectorSearch can only appear as the first stage of the aggregation pipeline or as the first stage of a $unionWith subpipeline. When using $vectorSearch, unless the user explicitly asks for the embeddings, $unset any embedding field to avoid reaching context limits." | ||
| ), | ||
| pipeline: z.array(z.union([AnyStage, VectorSearchStage])).describe( | ||
| `An array of aggregation stages to execute. | ||
| \`$vectorSearch\` **MUST** be the first stage of the pipeline, or the first stage of a \`$unionWith\` subpipeline. | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Unless proven otherwise by accuracy tests I fear this sounding more like $vectorSearch always has to be the first stage regardless of the pipeline needing one or not. Would it make sense to frame it like - |
||
| ### Usage Rules for \`$vectorSearch\` | ||
| - **Unset embeddings:** | ||
| Unless the user explicitly requests the embeddings, add an \`$unset\` stage **at the end of the pipeline** to remove the embedding field and avoid context limits. **The $unset stage in this situation is mandatory**. | ||
| - **Pre-filtering:** | ||
| If the user requests additional filtering, include filters in \`$vectorSearch.filter\` only for pre-filter fields in the vector index. | ||
| NEVER include fields in $vectorSearch.filter that are not part of the vector index. | ||
| - **Post-filtering:** | ||
| For all remaining filters, add a $match stage after $vectorSearch. | ||
kmruiz marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ### Note to LLM | ||
| - If unsure which fields are filterable, use the collection-indexes tool to determine valid prefilter fields. | ||
| - If no requested filters are valid prefilters, omit the filter key from $vectorSearch.` | ||
| ), | ||
| responseBytesLimit: z.number().optional().default(ONE_MB).describe(`\ | ||
| The maximum number of bytes to return in the response. This value is capped by the server's configured maxBytesPerQuery and cannot be exceeded. \ | ||
| Note to LLM: If the entire aggregation result is required, use the "export" tool instead of increasing this limit.\ | ||
|
|
||
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it SDK that is doing the boxing of Number to Int32, etc? wondering if that is something we should be doing everywhere else as well.