Skip to content

Add support for similar docs query #674

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 16, 2025

Pull Request

Related issue

Fixes #646

What does this PR do?

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

    • Introduced similarity search capabilities, allowing users to find documents similar to a specified document within an index.
    • Added configurable options for similarity queries, including pagination, filtering, attribute selection, and detailed ranking score information in the results.
  • Documentation

    • Provided example usage and detailed documentation for the new similarity search functionality.

Copy link

coderabbitai bot commented Jun 16, 2025

Walkthrough

A new module for similarity search has been introduced, including data structures and builder methods for constructing and executing similarity queries on an index. The Index struct now supports an asynchronous method to perform similar document queries. Relevant modules are publicly exposed, and internal visibility is adjusted for a serialization helper.

Changes

File(s) Change Summary
src/similar.rs New module: Implements similarity search query builder, result types, and async execution method.
src/indexes.rs Adds similar_query async method to Index for posting similarity queries. Imports similar.
src/lib.rs Publicly exposes the new similar module.
src/search.rs Increases visibility of serialize_with_wildcard to pub(crate).

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Index
    participant SimilarQuery
    participant HTTP

    Client->>Index: similar_query(&SimilarQuery)
    Index->>HTTP: POST /indexes/{uid}/similar (with SimilarQuery)
    HTTP-->>Index: SimilarResults<T>
    Index-->>Client: Result<SimilarResults<T>, Error>
Loading

Assessment against linked issues

Objective Addressed Explanation
Implement searchSimilarDocuments via POST /indexes/:uid/similar (#646)
Add builder and execution for similarity queries, including result/metadata structures (#646)
Expose new similar module and integrate with Index struct (#646)
No changes to embedders or vector/hybrid search settings/parameters (#646) These aspects are not addressed in this PR.

Assessment against linked issues: Out-of-scope changes

Code Change Explanation
Increased visibility of serialize_with_wildcard (src/search.rs) This change is not directly related to the implementation of similarity queries or endpoints. It may be preparatory or incidental, but is not required by the objectives.

Poem

In the warren of code, a new path appears,
For searching by likeness, across data frontiers.
With queries that wander and results that align,
The similar module hops in—oh, how divine!
Now bunnies can fetch, with a whisker’s delight,
Documents alike, in the soft moonlight.
🐇✨

✨ 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: 1

🧹 Nitpick comments (5)
src/lib.rs (1)

264-266: Consider keeping module declarations alphabetically sorted for quicker discoverability

similar is appended after utils, which breaks the existing (roughly) alphabetical ordering of the public mod list (search, settings, snapshots, …). Re-ordering modules helps future contributors locate items faster.

-/// Module related to similar queries and results.
-pub mod similar;
+/// Module related to similar queries and results.
+pub mod similar;          // move this so the list stays alphabetically ordered

Purely cosmetic – adjust only if you value the convention.

src/search.rs (1)

110-118: Visibility bump looks good; double-check companion helpers

Exposing serialize_with_wildcard as pub(crate) is necessary for the new similar module — nice catch.
If similar ever needs the crop helper as well (serialize_attributes_to_crop_with_wildcard), remember to apply the same visibility change or move both helpers to a shared utils sub-module to avoid future leakage.

src/similar.rs (3)

38-39: Clarify documentation for the id field

The comment "Search Doc ID" is ambiguous. Consider clarifying that this is the ID of the reference document used for the similarity search.

-    /// Search Doc ID
+    /// ID of the reference document used for the similarity search
     pub id: String,

212-214: Remove unnecessary clone in build method

The build method clones the entire query object unnecessarily. Consider returning a reference or removing this method if not needed.

-    pub fn build(&mut self) -> SimilarQuery<'a, Http> {
-        self.clone()
-    }
+    pub fn build(&self) -> &SimilarQuery<'a, Http> {
+        self
+    }

Alternatively, if the build method is not essential (since execute can be called directly), consider removing it entirely to simplify the API.


223-225: Fix typo and track embedder configuration

There's a typo in the comment, and the TODO indicates missing functionality.

 // TODO: set UserProvided EembdderConfig
 // Embedder have not been implemented
-// But Now It does't work
+// But Now It doesn't work

Would you like me to create an issue to track the implementation of embedder configuration functionality?

📜 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 8a2bded.

📒 Files selected for processing (4)
  • src/indexes.rs (2 hunks)
  • src/lib.rs (1 hunks)
  • src/search.rs (1 hunks)
  • src/similar.rs (1 hunks)
🔇 Additional comments (1)
src/indexes.rs (1)

1657-1669: LGTM!

The implementation correctly follows the established pattern for query methods and properly integrates with the similar module.

Comment on lines +1650 to +1651
/// let query = SimilarQuery::new(&movies, "1", "default").build();
/// let results = query.similar_query::<Movie>(&query).await.unwrap();
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix documentation example error

The example incorrectly calls similar_query on the query object instead of the movies index object.

 let query = SimilarQuery::new(&movies, "1", "default").build();
-let results = query.similar_query::<Movie>(&query).await.unwrap();
+let results = movies.similar_query::<Movie>(&query).await.unwrap();
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
/// let query = SimilarQuery::new(&movies, "1", "default").build();
/// let results = query.similar_query::<Movie>(&query).await.unwrap();
/// let query = SimilarQuery::new(&movies, "1", "default").build();
/// let results = movies.similar_query::<Movie>(&query).await.unwrap();
🤖 Prompt for AI Agents
In src/indexes.rs around lines 1650 to 1651, the documentation example
incorrectly calls similar_query on the query object instead of the movies index
object. Fix this by changing the call to similar_query to be on the movies index
object, passing the query as an argument, ensuring the example correctly
demonstrates usage.

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.

[v1.13] Stabilize AI-powered search
1 participant