Skip to content

Add support for returning document vector data when get one document #672

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JiaYingZhang
Copy link

@JiaYingZhang JiaYingZhang commented Jun 12, 2025

Pull Request

Related issue

What does this PR do?

  • Support return document vector data with get one document

PR checklist

Please check if your PR fulfills the following requirements:

  • Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
  • Have you read the contributing guidelines?
  • Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Summary by CodeRabbit

  • New Features
    • Added an option to include document vector data in search results.
  • Documentation
    • Updated usage examples to demonstrate how to enable retrieval of document vectors in queries.

Copy link

coderabbitai bot commented Jun 12, 2025

Walkthrough

A new optional boolean field, retrieve_vectors, was added to the DocumentQuery struct, along with a corresponding builder-style method for setting it. The constructor for DocumentQuery was updated to initialize this field, and the documentation example now demonstrates its usage.

Changes

File(s) Change Summary
src/documents.rs Added retrieve_vectors field and with_retrieve_vectors method to DocumentQuery; updated constructor and documentation example.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant DocumentQuery
    participant Index

    User->>Index: Obtain Index reference
    User->>DocumentQuery: Call DocumentQuery::new(&Index)
    User->>DocumentQuery: Call .with_fields(...)
    User->>DocumentQuery: Call .with_retrieve_vectors(true)
    Note right of DocumentQuery: Sets retrieve_vectors = Some(true)
    User->>DocumentQuery: Execute query
Loading

Poem

In the land of code, a field appears,
retrieve_vectors now calms your fears.
With builder style, your queries grow,
More options for docs, as you now know.
The rabbit hops with glee anew—
More data for all, just for you!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3130f8c and 161dff1.

📒 Files selected for processing (1)
  • src/documents.rs (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/documents.rs
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/documents.rs (1)

139-145: Builder method is correct but consider eliding the false case

When the user calls .with_retrieve_vectors(false) we still serialise retrieveVectors=false.
If the server treats the absence of the parameter as “false” already (which is common), sending an explicit false is redundant and increases payload size.

A leaner alternative:

-    pub fn with_retrieve_vectors(
-        &mut self,
-        retrieve_vectors: bool,
-    ) -> &mut DocumentQuery<'a, Http> {
-        self.retrieve_vectors = Some(retrieve_vectors);
+    pub fn with_retrieve_vectors(
+        &mut self,
+        retrieve_vectors: bool,
+    ) -> &mut DocumentQuery<'a, Http> {
+        if retrieve_vectors {
+            self.retrieve_vectors = Some(true);
+        } else {
+            self.retrieve_vectors = None;
+        }
         self
     }

This keeps the query string clean while still allowing an opt-in behaviour.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 90a153c and 3130f8c.

📒 Files selected for processing (1)
  • src/documents.rs (4 hunks)
🔇 Additional comments (2)
src/documents.rs (2)

91-96: Constructor update looks good

DocumentQuery::new now initialises retrieve_vectors to None, keeping backward compatibility (flag is absent unless explicitly set).
No issues spotted.


83-87:

❓ Verification inconclusive

Confirm query-string key matches the Meilisearch API

retrieve_vectors is serialized as retrieveVectors, which is camel-cased and differs from the usual snake-case keys (fields, limit, …).
Before merging, make sure the server really expects the exact key "retrieveVectors"; otherwise every call will silently drop the flag.

If no other occurrence is found or the API expects a different name (e.g. vector or returnVectors), adjust the rename attribute accordingly.


🏁 Script executed:

#!/bin/bash
# Grep for other occurrences so that the new key stays consistent
rg -n '"retrieveVectors"' --type rust

Length of output: 141


Verify Meilisearch search param “retrieveVectors”

The retrieve_vectors field is being serialized as retrieveVectors, which deviates from the usual snake_case query keys (fields, limit, …). We only found this single occurrence:

  • File: src/documents.rs
    Line 85: #[serde(skip_serializing_if = "Option::is_none", rename = "retrieveVectors")]

Before merging, please confirm in the Meilisearch API documentation that the search endpoint expects exactly "retrieveVectors". If the actual parameter name differs (for example, vector or returnVectors), update the rename attribute accordingly.

Copy link
Member

@irevoire irevoire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, thanks for the contribution

@JiaYingZhang JiaYingZhang force-pushed the doc-retrieve-vec-support branch from 3130f8c to 161dff1 Compare June 12, 2025 08:47
@JiaYingZhang JiaYingZhang requested a review from irevoire June 12, 2025 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants