sophie/homelab
0
0
Fork 0
Code Issues 3 Pull requests 17 Projects Releases Packages Wiki Activity Actions

chore(deps): update getmeili/meilisearch docker tag to v1.55.0 #33

Open
svc-renovate wants to merge 1 commit from renovate/getmeili-meilisearch-1.x into main
pull from: renovate/getmeili-meilisearch-1.x
merge into: sophie:main
Conversation 0 Commits 1 Files changed 1 +1 -1
svc-renovate commented 2026-10-22 21:54:12 +11:00
Collaborator
Copy link

This PR contains the following updates:

Package Update Change
getmeili/meilisearch minor v1.13.3 → v1.55.0

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

meilisearch/meilisearch (getmeili/meilisearch)

v1.55.0: 🔭

Compare Source

🌈 Improvements

Preview the effect of a dynamic search rule

Apply an inline-specified dynamic search rule to a search query.

Search query objects in the following endpoints now have an additional, optional inlineRule parameter.

When present and not null, then Meilisearch will check if query satisfies the conditions of the dynamic search rule specified in inlineRule, and if so will apply the actions of the rule as if it had been sent to the PATCH /dynamicSearchRule/{:uid} endpoint.

Additionally, if the Meili-Include-Metadata header is present in the request with the value true, then the metadata in the response will contain information about whether the conditions of the inline rule were satisfied and if not why.

Meilisearch Cloud will use this backend feature to implement a preview UI for dynamic search rules.

Using inlineRule requires Meilisearch Enterprise Edition and the dynamicSearchRules experimental feature.

By @​dureuill in #​6669

Details
  1. There is a new InlineRule object with the following field:
    1. uid, string, mandatory: unique ID of the rule. If there is already a rule with this id, then the inline rule will replace the existing rule for the duration of this search query.
    2. active, boolean, optional, defaults to true: whether the rule is active. The actions of an inactive inline rule never apply to the search, but its conditions are still checked
    3. conditions: RuleConditions object, identical to the conditions field in the body of PATCH /dynamic-search-rules/{:uid}
    4. actions: RuleActions object, identical to the actions field in the body of PATCH /dynamic-search-rules/{:uid}
    5. precedence: integer, optional, identical to the precedence field in the body of PATCH /dynamic-search-rules/{:uid}
  2. The POST /indexes/{:indexUid}/search body has an additional, optional (defaults to null) inlineRule field which is an InlineRule object.
  3. In the POST /multi-search body, the objects inside the queries array have an additional, optional (defaults to null) inlineRule field which is an InlineRule object.
Examples
Passing a search rule specific to the user making the request 
// POST /indexes/movies/search
{
  "q": "super hero",
  "inlineRule": {
    "uid": "user-likes-batman",
    "actions": {
      "scale": [
        {
          // filter recent Batman movies
          "filter": "hero = batman AND release_time = fresh",
          "weight": 1.2 // moderate relevancy boost
        }
      ]
    }
  }
}
Previewing the effect of a search rule 
// POST /multi-search -H 'Meili-Include-Metadata: true`

{
  "queries": [
    // base query without inline rule
    {
      "q": "fashion",
      "filter": "color = blue AND category = shirt"
    },
    // same query with inline rule
    {
      "q": "fashion",
      "filter": "color = blue AND category = shirt",
      "inlineRule": {
        "uid": "special-sales",
        "conditions": {
          "query": {
            "words": "pants",
          },
            "filter": {
              "values": {
                "color":  "yellow",
                "stock_intent": "destock"
            }
          }
        }
      }
    }
  ]
}

Response:

{
  // [ ... ] some other fields
  "results": [
    // results without the rule
    {
      "hits": [ ... ] // documents returned without the rule
    },
    // results with the rule
    {
      // [...] some other fields
      "hits": [...], // documents returned with the rule. Here the same, because the conditions of the rules are not satisfied
      "metadata": {
        // [...] some other fields
        "inlineRuleConditionOutcomes":  {
          "satisfiesActiveCondition": true,
          "satisfiesQueryWordsCondition": {
            "missingWord": "pants"
          },
        "satifiesFilterCondition": {
          "missingConstraintOnField": {
            "field":  "stock_intent"
          },
          "unmetConstraintOnField": 
            "field": "color"
          }
        }
      }
    }
  ]
}

Improve showPerformanceDetails at search time

When setting showPerformanceDetails to true in a search request, the response's performanceDetails will now display an entry for the facet distribution computation.

New trace entries

Request

curl -X POST 'http://localhost:7700/indexes/movies/search' \
  -H 'Content-Type: application/json' \
  -d '{
    "q": "batman",
    "facets": ["genres"],
    "showPerformanceDetails": true,
    "limit": 3
  }'

Response

{
    "hits": [
		# ...
    ],
    "query": "batman",
    "processingTimeMs": 4,
    "limit": 3,
    "offset": 0,
    "estimatedTotalHits": 68,
    "facetDistribution": {
        "genres": {
			#...
        }
    },
    "facetStats": {},
    "requestUid": "01a12f80-0e1b-7632-b4f3-c8d4914048c9",
    "performanceDetails": {
        "wait in queue": "68.58µs",
        "preprocess filters > prepare": "100.25µs",
        "preprocess filters": "100.42µs",
        "process > prepare": "115.54µs",
        "process > send to remote": "102.71µs",
        "process > execute local > load field ids map": "30.88µs",
        "process > execute local > query[0] > tokenize query": "265.38µs",
        "process > execute local > query[0] > evaluate query": "890.96µs",
        "process > execute local > query[0] > keyword ranking": "425.04µs",
        "process > execute local > query[0]": "2.95ms",
        "process > execute local > pin hits": "9.92µs",
        "process > execute local > format": "94.62µs",
        "process > execute local > facet distribution > compute facet distribution": "315.75µs",
        "process > execute local > facet distribution > compute facet stats": "27.71µs",
        "process > execute local > facet distribution": "432.62µs",
        "process > execute local": "3.81ms",
        "process > wait for remote": "50.96µs",
        "process > merge": "905.62µs",
        "process": "5.07ms"
    }
}

Three additional steps:

        "process > execute local > facet distribution > compute facet distribution": "315.75µs",
        "process > execute local > facet distribution > compute facet stats": "27.71µs",
        "process > execute local > facet distribution": "432.62µs",

By @​ManyTheFish in #​6644

🦋 Fixes

Avoid panic at search time during formatting

Documents containing raw unicode codepoints (e.g. \u03b1) would cause a panic at search time when formatting results for highlighting when using some segmenters.

A failure at the segmenter's level no longer causes a panic.

By @​dureuill in #​6673

Fix search performance of ranking score threshold

[!IMPORTANT]
This fix modifies the relevancy of the engine in some circumstances. This is allowed as per our back-compatiblity policy.

To avoid a performance sink when using the rankingScoreThreshold parameter in a search, Meilisearch now guarantees that the search will stop after evaluating the first document whose score is below the threshold. Previously Meilisearch would try to evaluate more documents, which could lead to evaluating all documents in the database, causing a very long search time.

By @​ManyTheFish in #​6661

Prevent unsupported binaryQuantization deactivation in embedder settings

[!WARNING]
This fix introduces a breaking change in the Meilisearch API. Because the previous behavior would corrupt the embeddings in the database, this is allowed by our back-compatibility policy.

Since the exact value of embeddings is not retained when the embedder is configured for binary quantize embeddings, disabling the binary quantization on an index is not allowed.

Unfortunately, an oversight in the API allowed to accidentally disable binary quantization by passing binaryQuantization: null in a setting update. This now results in an error.

By @​dureuill in #​6656

🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.54.3...v1.55.0

v1.54.3

Compare Source

This release contains an important stability fix for Meilisearch. Update from v1.54.2 is recommended.

See #​6658 for details

v1.54.2

Compare Source

Meilisearch v1.54.2 contains an important fix for users of the dynamicSearchRule experimental feature.

🦋 Fixes

  • Trying to process, display, delete or cancel dynamic search rules update tasks that were created in Meilisearch v1.53 or prior no longer causes internal errors. By @​dureuill in #​6651. Thanks to @​connorabbas for their report in #​6646 ❤️

v1.54.1

Compare Source

🪲 Bug fixes
🔩 Miscellaneous

v1.54.0

Compare Source

💥 Breaking Changes

Meilisearch v1.54.0 makes breaking changes to the dynamicSearchRules experimental features.

  • For Cloud users, rules will be migrated automatically, and the UI will adapt to the new API. Only the first change on rulelist might affect users that directly get rules through the API.
  • If upgrading with --upgrade-db, rules will be migrated automatically.

  1. The POST /dynamic-search-rules endpoint now returns actions as an object with 2 fields instead of a list:

  2. pin is an array of Pin objects with the following fields:

    1. id, String, mandatory: document id of the document to pin
    2. position: positive or zero number, mandatory: position where to pin the document
    3. indexUid, optional, defaults to null, uid of the index that this action applies to. If null or missing, the action applies to any index containing a document with the provided id.

  3. scale is an array of Scale objects with the following fields:

    1. weight, positive or zero number, mandatory: scaling factor to multiply with the selected documents' innate relevancy score
    2. ids, array of strings, optional: list of document ids whose document's relevancy score should be scaled by the provided weight
    3. filter: Meilisearch filter without a foreign filter, optional: a filter on the index that is resolved to determine a list of selected documents
    4. indexUid, optional, defaults to null, uid of the index that this action applies to. If null or missing, the action applies to any index.

  4. The PATCH /dynamic-search-rules/{:ruleUid} endpoint now expects a rule with the modified actions field. See changes to POST /dynamic-search-rules for details.

  5. The uid __meilisearch_metadata is now reserved and cannot be used as a ruleUid in PATCH /dynamic-search-rules/{:ruleUid}

🌈 Enhancements

Boost, demote and hide documents with search rules

  • A dynamic search rule can now boost, deboost or hide documents by defining a new "scale" action that selects some documents by filter and/or an explicit list of ids and exposes a scale factor as a weight:
    • If the weight is > 1.0, then the selected documents are boosted
    • If the weight is < 1.0, then the selected documents are deboosted (demoted)
    • If the weight is = 0.0, then the selected documents are hidden and don't appear in search results (unless if they are also pinned)
    • ⚠️ Because the factor is applied to the relevancy rules, it has little measurable effect when the first ranking rule is not a relevancy rule.
  • Score details for a pinned document now contains an additional ruleUid field indicating the name of the rule that resulted in the document being pinned. ⚠️ As a result, end-users can find out the uid of applied rules by looking at ranking score details. Please keep any sensitive information in the description of the rule instead ⚠️
  • Score details for a scaled document now contains an additional scale field, with order 0. The scale field is an object with the following fields:
    • order: order of application of the rule. Always 0
    • actions: an array of ScaleActions, where each ScaleAction contains the following fields:
      • ruleUid: the name of the rule that was applied
      • weight the weight of the rule that was applied
    • totalWeight: the total multiplicative factor computed as the product of the individual .actions[].weight.
  • New environment variables controlling how much scale operations can occur:
    • MEILI_EXPERIMENTAL_DSR_FUEL_MAX_SCALE_ACTIONS: maximum number of applicable (at least one selected document) scale actions in a single search. Range 1-255, default 10
    • MEILI_EXPERIMENTAL_DSR_FUEL_SCALE_FUEL: maximum number of combinations of scale constraint that are evaluated in a single search. Range 1-255, default 10.
Examples
Boosting "Batman" product for a festival
  1. Creating the search rule
// PATCH /dynamic-search-rule/batman-festival

{
  "conditions": {
    "time": {
      "start": "2026-09-21T19:00:00Z",
      "end": "2026-09-28T18:59:00Z"
    },
  },
  "actions": {
    "scale": [
      {
        "filter": "series = batman",
        "weight": 4.0
      }
    ]
  }
}
  1. Once the DSR update task has been processed and the festival begins on September 21st, make a search query:
{
  "q": "superhero returns prequel",
  "showRankingScoreDetails": true
}
  1. Observe the ranking of documents

"hits": [
        {
          "id": "batman-returns",
          "title": "Batman Returns",
          "series": "batman",
          "_rankingScore": 0.30808080808080807,
          "_rankingScoreDetails": {
            "scale": {
              "order": 0,
              "actions": [
                {
                  "ruleUid": "batman-festival",
                  "weight": 4.0
                }
              ],
              "totalWeight": 4.0
            },
            "words": {
              "order": 1,
              "matchingWords": 1,
              "maxMatchingWords": 3,
              "score": 0.3333333333333333
            },
            "typo": {
              "order": 2,
              "typoCount": 0,
              "maxTypoCount": 1,
              "score": 1.0
            },
            "proximity": {
              "order": 3,
              "score": 1.0
            },
            "attributeRank": {
              "order": 4,
              "score": 1.0
            },
            "wordPosition": {
              "order": 5,
              "score": 0.9090909090909092
            },
            "exactness": {
              "order": 6,
              "matchType": "noExactMatch",
              "matchingWords": 1,
              "maxMatchingWords": 1,
              "score": 0.3333333333333333
            }
          }
        },
        {
          "id": "superman-returns",
          "series": "superman",
          "title": "Superman Returns - The Prequels",
          "_rankingScore": 0.9628456221198156,
          "_rankingScoreDetails": {
            "words": {
              "order": 0,
              "matchingWords": 3,
              "maxMatchingWords": 3,
              "score": 1.0
            },
            "typo": {
              "order": 1,
              "typoCount": 0,
              "maxTypoCount": 3,
              "score": 1.0
            },
            "proximity": {
              "order": 2,
              "score": 0.5714285714285714
            },
            "attributeRank": {
              "order": 3,
              "score": 1.0
            },
            "wordPosition": {
              "order": 4,
              "score": 0.9032258064516128
            },
            "exactness": {
              "order": 5,
              "matchType": "noExactMatch",
              "matchingWords": 2,
              "maxMatchingWords": 3,
              "score": 0.25
            }
          }
        },
        // ...
      ],
      "processingTimeMs": "[duration]",
      "limit": 20,
      "offset": 0,
      "estimatedTotalHits": 42,
      "requestUid": "[uuid]"
    }
Demoting out-of-stock products 
// PATCH /dynamic-search-rules/out-of-stock

{
  "actions": {
    "scale": [
      {
        "filter": "availability = \"out of stock\"",
        "weight": 0.5
      }
    ]
  }
}
Hiding discontinued products 
// PATCH /dynamic-search-rules/discontinued

{
  "actions": {
    "scale": [
      {
        "filter": "availability = discontinued",
        "weight": 0.0
      }
    ]
  }
}

By @​dureuill in #​6549

MCP endpoint

We introduce a new MCP protocol on the /mcp path. It implements the HTTP+SSE Transport version of the protocol. You can register the Meilisearch MCP in your favorite LLM, e.g., Claude Code, Codex. Note that the MCP route is using bearer authentication and doesn't support OAuth authentication.

Enable the mcpRoute experimental feature to use the feature.

by @​Kerollmops in #​6629

Improve search performance details in multi-search

The performance details in a federated search now separate the timing per query

Example 
"performanceDetails": {
  "wait in queue": "1.36ms",
  "preprocess filters > prepare": "985.00µs",
  "preprocess filters > send to remote": "220.00µs",
  "preprocess filters > execute local > evaluate filter": "139.00µs",
  "preprocess filters > execute local": "1.61ms",
  "preprocess filters > wait for remote": "35.97ms",
  "preprocess filters": "39.01ms",
  "process > prepare": "96.00µs",
  "process > send to remote": "118.00µs",
  "process > execute local > load field ids map": "63.00µs",
  "process > execute local > query[0] > evaluate filter": "84.00µs",
  "process > execute local > query[0] > tokenize query": "163.00µs",
  "process > execute local > query[0] > evaluate query": "116.00µs",
  "process > execute local > query[0] > keyword ranking": "634.00µs",
  "process > execute local > query[0]": "1.52ms",
  "process > execute local > pin hits": "29.00µs",
  "process > execute local > format": "36.00µs",
  "process > execute local": "2.90ms",
  "process > wait for remote": "37.24ms",
  "process > merge": "82.00µs",
  "process": "40.45ms",
  "hydrate > send to remote": "38.00µs",
  "hydrate > execute local": "35.00µs",
  "hydrate > wait for remote": "41.00µs",
  "hydrate": "295.00µs",
  "merge facets": "51.00µs"
}

By @​ManyTheFish in #​6631

🔩 Miscellaneous

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.53.2...v1.54.0

v1.53.3

Compare Source

This release contains an important stability fix for Meilisearch. Update from v1.53.2 is recommended.

See #​6658 for details

v1.53.2: 🖇️​

Compare Source

🪲 Bug fixes

🔒 Security

🔩 Miscellaneous

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.53.1...v1.53.2

v1.53.1: 🖇️​

Compare Source

✨ Enhancement

Add an env var to change the task queue readers

by @​ManyTheFish in #​6587

Control the maximum number of LMDB read transactions at the same time for the task queue.

The following environment variable can be exported to specify the maximum number of simultaneous read transactions:


# Only the environment variable can set this parameter
MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS=100

Product discussion: https://github.com/orgs/meilisearch/discussions/806

🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.53.0...v1.53.1

v1.53.0: 🖇️​

Compare Source

✨ Enhancement

  • Sharding for foreign filters by @​ManyTheFish in #​6517

    • The foreign filter now supports sharding by retrieving the documents through the network when evaluating the foreign filters and hydrating the documents.

    • The limit of documents that a foreign filter can retrieve has been increased from 100 to 1000.

  • Adds indexSize and usedIndexSize returned by GET /indexes/{index_uid}/stats and in GET /stats by @​tpayet in #​6563

🔒 Security
🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.51.0...v1.53.0

v1.52.4

Compare Source

This release contains an important stability fix for Meilisearch. Update from v1.52.3 is recommended.

See #​6658 for details

v1.52.3: 🐠

Compare Source

🪲 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.52.2...v1.52.3

v1.52.2: 🐠

Compare Source

🪲 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.52.1...v1.52.2

v1.52.1: 🐠

Compare Source

🪲 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.52.0...v1.52.1

v1.52.0: 🐠

Compare Source

✨ Enhancement
  • Introduce the /tasks/stream and /batches/stream SSE routes by @​Kerollmops in #​6533
    This experimental feature allows establishing a live connection to the engine, avoiding the need to implement long polling and instead letting the engine provide new tasks, batches, and batch progress in a push-based manner. Using this route can drastically reduce network load when retrieving the status of a Meilisearch instance.
  • Speed up the search a bit more by @​Kerollmops in #​6542
    We improve the search speed when it comes to formatting the documents by making an O(n) operation, where n is the number of retrieved documents, become an O(1) operation. This improvement can significantly increase search speed when requesting a large (> 20) number of documents.
🪲 Bug fixes

v1.51.0: 👽

Compare Source

✨ Enhancement
New filter rule activation condition
Dynamic search rules (DSR) can now declare a new `filter` condition: it contains a single `values` key, whose value is a JSON object.
The keys of this `values` JSON object are the facet names (e.g., `color`, `genres`, ...), while their values are the values that a filter must resolve to for these facets, so that the rule is active.

<details>

<summary>Example of sending a DSR with a filter condition</summary>

```jsonc
// PATCH /dynamic-search-rules/test-filter

{
  "conditions": {
    "filter": {
      "values": {
        "color": "red",
        "category": "shirt"
      }
    }
  },
  "actions": [
    {
      "selector": { "id": "red shirt on sales" },
      "action": { "type": "pin", "position": 0 }
    }
  ]
}
```

</details>

<details>
<summary>Example of search query that enables the DSR above</summary>

```jsonc
{
  "filter": "(category = shirt AND color = red) OR (category = jeans AND color = blue)"
}
```

</details>

Note that the filter only needs to have one branch resolving to all the facet values declared in the rule for the rule to be active.
New lastUpdatedAt field
Dynamic search rules returned by `GET /dynamic-search-rules/{:ruleUid}` and `POST /dynamic-search-rules` contain an additional `lastUpdatedAt` field. 

This field is automatically updated with the `enqueuedAt` value of the last task that modified the rule.
Rules are listed with the most recently updated first
`POST /dynamic-search-rules` now lists rules in descending `lastUpdatedAt` order, meaning that the most recently updated rules will be listed first.
New environment variables
New environment variables are defined to control the behavior of the DSR fuel:

- `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_FUEL` (in range 0..4294967296): controls how many filter constraint combinations Meilisearch will attempt to resolve at search time before giving up and applying partial rules.
- `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_OR_FUEL` (in range 0..65536): controls how many filter disjunctions Meilisearch will build when turning a filter to its canonical shape
- `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_AND_FUEL` (in range 0..65536): controls how many filter conjunctions Meilisearch will build in total when turning a filter to its canonical shape
- `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_DEPTH_FUEL` (in range 0..256): controls the maximum recursive depth that Meilisearch allows when turning a filter to its canonical shape

  • Speed up search requests by @​Kerollmops in #​6528
    Improves Meilisearch search speed by avoiding unnecessary internal work. We drastically reduced the number of times we retrieve data from disk to a single time across the whole search pipeline. This improvement will have the greatest effect on datasets with a large number of distinct fields across documents. We have seen search speeds up to 5.4x on a dataset with more than 14k different fields.

  • Stabilize dumpless upgrade by @​curquiza in #​6486

    ⚠️ Breaking change following the stabilization of an experimental feature ⚠️

    The flag —-experimental-dumpless-upgrade is renamed —-upgrade-db, keeping the exact same behavior.

  • Remove unused experimental features by @​curquiza in #​6489

    ⚠️ Breaking change: removing the following experimental features ⚠️

🪲 Bug fixes
  • Make sure legacy attribute patterns work by @​Kerollmops in #​6531
    • Missing support for the shorthand filterable attributes syntax
🔩 Miscellaneous

New Contributors

v1.50.0: 🐐

Compare Source

Meilisearch v1.50 revamps the Dynamic Search Rules, adds support for federated document fetch in sharded configurations, among other improvements

Breaking changes

This release introduces breaking changes for users using some experimental features

dynamicSearchRules experimental feature
Request type changes
  1. priority has been replaced with precedence, which better reflects the behavior (lower precedence means the rule is applied first)
  2. conditions has been modified from an array to an object with two fields: "query" of type QueryCondition and "time" of time TimeCondition
  3. New type QueryCondition that contains the fields isEmpty (as previously) and words instead of contains (same type)
  4. It is now possible to pass isEmpty: false with words in a QueryCondition. Passing isEmpty:true with words still results in a synchronous error.
  5. New type TimeCondition with fields start and end (unchanged semantics from previous type).
  6. When specifying the selector of an Action, it is now mandatory to specify an id. Previously, it was optional, but the action would never trigger.
  7. When listing rules with POST /dynamic-search-rules, filter.attributePatterns has been replaced with filter.query, an optional string that searches in rule description and conditions.query.words.
  8. When calling DELETE /dynamic-search-rules/{:ruleUid} or PATCH /dynamic-search-rules/{:ruleUid} in a sharded configuration, endpoint will not return a HTTP 400 error if called on a follower remote rather than on the leader.
Response changes
  1. PATCH /dynamic-search-rules/{:ruleUid} and DELETE /dynamic-search-rules/{:ruleUid} now register an asynchronous task..
  2. The response is modified to return the registered task instead of the modified dynamic search rule.
  3. HTTP 404 is no longer returned if the {:ruleUid} portion of the URL refers to a rule that doesn't exist. This is because rules are processed asynchronously, and is consistent with the behavior of DELETE /indexes/{:indexUid}/documents/{:docId} for {:docId}
network experimental feature

The default behavior for users using the network experimental feature with sharding configured (leader not null) will change on the following routes:

  • GET indexes/:uid/documents
  • GET indexes/:uid/documents/:document_id
  • POST indexes/:uid/documents/fetch

Meilisearch will now fetch the documents from all the shards and not only on the local machine when processing the request.
To keep the same behavior as before, users will have to set useNetwork to false when making their request.

🌈 Improvements

Scaling up the Dynamic Search Rules
  • Dynamic search rules scale up to 75K rules without any impact on the search
  • The API of Dynamic Search Rules has been simplified
    • It is harder to send conditions that will result in the rules never activating
  • This also unlocks future improvements such as filter activation conditions for search rules
Additions
  • Add a new DELETE /dynamic-search-rule route that deletes all the DSRs
  • Add the concept of "DSR fuel" that determines how much energy is spent resolving DSR during a search. The fuel is initialized with some default variables that can be overridden using environment variables:
    • MEILI_EXPERIMENTAL_DSR_FUEL_MAX_COUNTED_WORDS: max number of words considered inside of a search query for the purpose of finding conditions.query.words constraints. Defaults to 10, max value is 255
    • MEILI_EXPERIMENTAL_DSR_FUEL_MAX_ACTIVE_RULES: max number of active rules whose actions are evaluated. Defaults to 1000, max value is 4294967
    • MEILI_EXPERIMENTAL_DSR_FUEL_MAX_PIN_ACTIONS: max number of pin actions that are applied. Defaults to 100, max value is 4294967
    • MEILI_EXPERIMENTAL_DSR_FUEL_WORD_FUEL: max number of constraint combinations that are evaluated for the purpose of finding conditions.query.words constraints. Defaults to 4096, max value is 4294967

By @​dureuill in #​6484 and #​6506

Behavior changes
  • The conditions.query.words behaves differently from query.contains: previously, a rule would match if its conditions query.contains would be substrings of q in the search query in the sense of str::contains. Now, a rule matches if all the words in conditions.query.words appear in q (after normalization). For q = hero super, query.contains = super hero would not match, whereas conditions.query.words = super hero does now match. This behavior is more in line with regular search, and allows improving performance.
  • Dynamic search rules are now replicated from the leader to its follower, when in a sharded configuration
Federated document fetch routes

GET indexes/:uid/documents, GET indexes/:uid/documents/:document_id and POST indexes/:uid/documents/fetch will now fetch the documents from all the shards in the configured network.

Moreover, a new useNetwork parameter is available to activate or deactivate the usage of the network.

By @​ManyTheFish in #​6495

Support partial wildcards when requesting facets

The facets parameter in search and federated search now supports more wildcards. Previously, only the single wildcard "*" was supported, requesting all filterable fields.

Now, patterns containing * are supported with the same matching rules as in filterableAttributes.attributePatterns and localizedAttributes.attributePatterns, such as dogs.*, which will add to the facet distribution all filterable fields that match the pattern (such as dogs.intel, dogs.kefir, etc.).

By @​Kerollmops in #​6497

🦋 Fixes

Fix migration from v1.48 and earlier

Migration via --experimental-dumpless-upgrade would fail in some cases in v1.49, when trying to migrate synonyms that contained no words (empty synonyms, or containing only separator tokens such as &).

Such synonyms are now ignored during migration, avoiding the issue.

By @​Kerollmops in #​6501

Fix filter memory consumption in some cases

In some conditions, the memory consumption of filters would increase quadratically with the length of the filter. This is now resolved for these cases.

By @​ManyTheFish in #​6509

No longer reject some correctly-escaped filters

Fix a bug where some filters containing escaped characters (such as \) would cause search requests to fail with invalid_search_filter

By @​dureuill in #​6499

More fault-tolerant S3 snapshots

Potentially fix an issue when sending a request to AWS S3 to create a new multipart upload, ensuring we resend the request if it fails.

By @​Kerollmops in #​6494

🔩 Miscellaneous changes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.49.0...v1.50.0

v1.49.0: 🪺

Compare Source

✨ Enhancement
  • Improve the synonyms storage by @​Kerollmops in #​6466
    We improve synonyms' performance by changing how we store and retrieve them during query processing. Users may have experienced performance issues when the number of synonyms in an index was high, resulting in a significant impact on search performance. The Meilisearch support team advised moving the settings and synonyms-as-keywords to the dedicated documents. This is no longer an issue; synonyms are loaded lazily, only when a word matches a synonym. You can see performance improvements of up to 13x, depending on the number of synonyms.
🔩 Miscellaneous

v1.48.3: v1.48.3 🫎​

Compare Source

🪲 Bug fixes

  • Fix a rare S3 snapshots bug by @​Kerollmops in #​6472

    We fixed a rare bug that could appear when using the S3 snapshot system. The bug is a race condition that occurs when we try to recycle internal buffers to reduce memory usage, which can cause an internal error and abort the snapshot upload.

  • Avoid remote search to return the same document twice by @​ManyTheFish in #​6473

    When using the remote federated search, Meilisearch was returning the same document twice from different machines. This was due to an internal filter that was not forwarded properly to the remote instances.

🔩 Miscellaneous

New Contributors

Thanks to @​0xfandom, who made his first contribution in #​6468 🎉

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.48.2...v1.48.3

v1.48.2: 🫎

Compare Source

Meilisearch v1.48.2 and Meilisearch v1.47.1 address CVE-2026-57823 and CVE-2026-57824.
We recommend updating if you are in one of the following situations:

  1. You have API keys where indexes is not ["*"] and where actions contains more permissions than: ["search", "documents.*", "indexes.*", "tasks.cancel", "tasks.delete", "tasks.get", "settings.*", "stats.*", "fields.post"]
  2. You have search tenant tokens and either an embedder or a chat workspace
  • We recommend that users of Meilisearch v1.48 update to Meilisearch v1.48.2
  • We recommend that users of Meilisearch v1.47 or lower update to Meilisearch v1.47.1

These versions both fix the following:

  1. CVE-2026-57824: Improper authentication leads to privilege escalation: an authenticated user with an index-scoped API and the appropriate set of actions could use global actions to read and write the global state of the Meilisearch instance. Possibly impacted users of Meilisearch Cloud were contacted ahead-of-time.
  2. CVE-2026-57823: Improper authentication leads to information disclosure: a user with a search tenant token could get some limited information about the existence of a document outside of the scope of the search rules attached to the tenant token, an indirect information about the content of the document.

We detected no trace of exploitation of these vulnerabilities.

We thank PuH4ck3rX for reporting these vulnerabilities ❤️

v1.48.1: 🫎

Compare Source

Revert #​6432 due to a dumpless upgrade bug report.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.48.0...v1.48.1

v1.48.0: 🫎​

Compare Source

✨ Enhancement

[Experimental] Render 🫎​ template route

by @​Mubelotix in #​5765

Introduces a new POST /render-template route that can be used to render any template or fragment on any input and associated renderRoute experimental feature that gates access to the route.

This route can be used to test document templates and fragments before and after having configured an embedder.

A body payload for the route is of the form:

{
  "template": /* templateTarget object */,
  "input": /* inputTarget object or null */
}

where template describes the template or fragment to render, and input describes what to use to render the template.

Upon calling this route, Meilisearch responds with:

{
  "template": "{{doc.text}}",
  "rendered": "template text after rendering using the input"
}

where template contains the unrendered base text of the document template, or the unrendered base JSON object of a fragment, and rendered contains the result of rendering the template of the chosen input.

If input is null in the request, then rendered is null in the response, and the route can be used solely to retrieve a template or fragment from the settings of an index.

Before calling the route

The API of this route is subject to change, so before calling this route, please enable the renderRoute experimental feature:

PATCH /experimental-features --json '{"renderRoute": true}'
Examples
  1. Rendering a document from an index on a document template from an embedder of that index
request 
// POST /render-template

{
  "template": {
    "kind": "documentTemplate",
    "indexUid": "movies",
    "embedder": "myMoviesEmbedder"
  },
  "input": {
    "kind": "indexDocument",
    "indexUid": "movies",
    "id": "2"
}
response 
{
  "template": "A movie titled {{doc.title}} whose description starts with {{doc.overview|truncatewords:10}}",
  "rendered": "A movie titled Ariel whose description starts with Taisto Kasurinen is a Finnish coal miner whose father has..."
}
  1. Rendering an inline document on a fragment from an embedder of an index
request 
// POST /render-template

{
  "template": { 
    "kind": "indexingFragment", 
    "indexUid": "dogs", 
    "embedder": "multi",
    "fragment": "captionedImage" 
  },
  "input": { 
    "kind": "inlineDocument", 
    "inline": { // pass your document inline as a JSON object
      "kind": "dog",
      "name": "iko",
      "breed": "jack russell",
      "mime": "image/png",
      "image": "/9j/4AAQSk..."
    } 
  }
}
response 
{
  "template": {
    "content": [
      {
        "type": "text",
        "text": "A picture of a {{doc.kind}} of breed {{doc.breed}}"
      },
      {
        "type": "image_base64",
        "image_base64": "data:{{doc.mime}};base64,{{doc.image}}"
      }
    ]
  },
  "rendered": {
    "content": [
      {
        "type": "text",
        "text": "A picture of a dog of breed jack russell"
      },
      {
        "type": "image_base64",
        "image_base64": "data:image/png;base64,/9j/4AAQSk..."
      }
    ]
  }
}
  1. Rendering a search query on a search fragment from a multimodal embedder of an index
request 
// POST /render-template
{
  "template": { 
    "kind": "searchFragment", 
    "indexUid": "testIndex", 
    "embedder": "testEmbedder",
    "fragment": "justBreed"
  },
  "input": {
    "kind": "inlineSearch",
    "inline": { // pass the search query inline
      "q": "unused",
      "media": {
        "name": "iko",
        "breed": "jack russell"
      },
      "filter": "ignored"
    }
  }
}
response 
    {
      "template": "It's a {{ media.breed }}",
      "rendered": "It's a jack russell"
    }
  1. Rendering an inline document on the document template from the chat settings of an index
request 
// POST /render-template

{
  "template": {
    "kind": "chatDocumentTemplate",
    "indexUid": "movies"
	// no embedder to specify since chat document template is global to index
  },
  "input": {
    "kind": "indexDocument",
    "indexUid": "movies",
    "id": "2"
}
response 
{
  "template": "{% for field in fields %}{% if field.is_searchable and field.value != nil %}{{ field.name }}: {{ field.value }}\n{% endif %}{% endfor %}",
  "rendered": "id: 2\ntitle: Ariel\noverview: Taisto Kasurinen is a Finnish coal miner whose father has just committed suicide and who is framed for a crime he did not commit. In jail, he starts to dream about leaving the country and starting a new life. He escapes from prison but things don't go as planned...\ngenres: DramaCrimeComedy\nposter: https://image.tmdb.org/t/p/w500/ojDg0PGvs6R9xYFodRct2kdI6wC.jpg\nrelease_date: 593395200\n"
}
  1. Rendering a document from an index on an inline document template
request 
// POST /render-template

{
  "template": {
    "kind": "inlineDocumentTemplate",
    "inline": "You can pass templates inline as well: nice to test them! {{doc.id}}"
  },
  "input": {
    "kind": "indexDocument",
    "indexUid": "movies",
    "id": "2"
}
response 
{
  "template": "You can pass templates inline as well: nice to test them! {{doc.id}}",
  "rendered": "You can pass templates inline as well: nice to test them! 2"
}
  1. Rendering an inline document on an inline indexing fragment
request 
// POST /render-template

{
  "template": {
    "kind": "inlineFragment",
    "inline": {
      "json_maps": "supported for fragments",
      "any_string": "is in liquid format: {{doc.test}}"
    }
  },
  "input": {
     "kind": "inlineDocument",
    "inline": {
      "test": true
    }
  }
}
response 
{
  "template": {
    "json_maps": "supported for fragments",
    "any_string": "is in liquid format: {{doc.test}}"
  },
  "rendered": {
    "json_maps": "supported for fragments",
    "any_string": "is in liquid format: true"
  }
}

[Experimental] Only support foreign filters on retrieval routes

by @​ManyTheFish in #​6446

Foreign filters are meant to be used in a retrieval context (search, get document...), but all the actions related to writing or modifying a document could have several unexpected behaviors if foreign filters are accepted.
We prefer forbidding the usage of this feature on the writing routes.

The following routes do not support Foreign-filter anymore:

Additional change: we now ensure that the experimental features are checked when parsing a filter

🪲 Bug fixes

🔒 Security

🔩 Miscellaneous

❤️ Thanks again to @​genisis0x and @​antcybersec

v1.47.1: 🦇

Compare Source

Meilisearch v1.48.2 and Meilisearch v1.47.1 address CVE-2026-57823 and CVE-2026-57824.
We recommend updating if you are in one of the following situations:

  1. You have API keys where indexes is not ["*"] and where actions contains more permissions than: ["search", "documents.*", "indexes.*", "tasks.cancel", "tasks.delete", "tasks.get", "settings.*", "stats.*", "fields.post"]
  2. You have search tenant tokens and either an embedder or a chat workspace
  • We recommend that users of Meilisearch v1.48 update to Meilisearch v1.48.2
  • We recommend that users of Meilisearch v1.47 or lower update to Meilisearch v1.47.1

These versions both fix the following:

  1. CVE-2026-57824: Improper authentication leads to privilege escalation: an authenticated user with an index-scoped API and the appropriate set of actions could use global actions to read and write the global state of the Meilisearch instance. Possibly impacted users of Meilisearch Cloud were contacted ahead-of-time.
  2. CVE-2026-57823: Improper authentication leads to information disclosure: a user with a search tenant token could get some limited information about the existence of a document outside of the scope of the search rules attached to the tenant token, an indirect information about the content of the document.

We detected no trace of exploitation of these vulnerabilities.

We thank PuH4ck3rX for reporting these vulnerabilities ❤️

v1.47.0: 🦇

Compare Source

🌈 Enhancements

Search personalization on federated search

We now support using the search personalization feature on federated search requests.

Like page/hitPerPage or limit/offset, the personalization option must be specified in the federation attribute to work properly.
Otherwise, an error will be returned reminding you to move the attribute in federation.

By @​ManyTheFish in #​6414

The new settings indexer is feature complete 🎉

  • We now better support the tokenizer-related settings
  • We improved the quality of the new settings indexer to enhance the engine's performance when changing the locales, the dictionary, synonyms, stop words, separator, and non-separator tokens.
  • This makes the new settings indexer feature-complete, meaning that, unless you set the MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS environment variable to true, all settings tasks can now be handled by the new settings indexer, bringing a better scaling behavior, much faster cancellation, and a more precise progress view.

By @​Kerollmops in #​6409

Observability improvements

We expose more Prometheus metrics to improve observability, specifically to show more metrics on document throughput and ease debugging.

By @​Kerollmops in #​6430

🦋 Fixes

  • Putting attributeRank/ wordPosition before words in the rankingRules list will no longer remove hits from the response, by @​pjdurden in #​6437
  • Meilisearch will no longer ignore the searchCutoffMs in some conditions when embedding documents, by @​dureuill in #​6447
  • Meilisearch will no longer fail to proxy a search request with a filter containing a ' during remote federated search or useNetwork: true search requests, by @​dureuill in #​6445

🔒 Security

🔩 Misc. changes

Search implementation refactor

Refactor the search pipeline to mutualize the code.
The new implementation will always perform a federated search under the hood, and then the output will be transformed into the expected route's output.

Noticeable changes from the user perspective:

  • Some error messages have been modified
  • Small breaking change: a few error codes change, such as MultiSearch<Error> <--> Search<Error>

Other changes

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.46.1...v1.47.0

v1.46.1: 🦆

Compare Source

Queue documents fetch routes

Add an experimental feature, queueDocumentsFetch, forcing the routes GET indexes/:uid/documents and POST indexes/:uid/documents/fetch to wait in the search queue if there is no available thread to process them.

v1.46.0: 🦆

Compare Source

This release introduces fixes for a regression in v1.45.0, where we were batching deletions by filter with other deletions or additions. It also enables the new settings indexer to support more parameters, making the engine faster to index documents when those settings are specified.

✨ Enhancement

  • Support exact and disable on numbers in the new settings indexer by @​Kerollmops in #​6398
    Introduce support for exact words and disable-on-words parameters in the new settings indexer, making the engine more efficient when changing these settings.

  • Support computing prefixes in the new settings indexer by @​Kerollmops in #​6391
    Support for the prefix search settings in the new settings indexer, so that changing this parameter makes the engine more efficient.

🪲 Bug fixes

  • Better limit read bytes when creating the S3 multipart part by @​Kerollmops in #​6405
    This fixes an issue we had with the multipart part size by ensuring we never construct a part larger than the defined multipart part size. With this fix, we always create a multipart with the provided multipart part size, except for the last part. Thanks, @​vidit-virmani, for the help investigating the issue.

  • Batch of documentDeletionByFilter with documentAdditionOrUpdate by @​Kerollmops and @​ManyTheFish in #​6415
    Correctly implement the support for auto-batching deletion by filter with document replacement and updates. This fixes a regression introduced in v1.45.0.

  • Fix a panic with incomplete filters by @​Kerollmops in #​6421
    Fixes an internal panic when a filter is incomplete by returning an error instead.

🔒 Security
🔩 Miscellaneous

v1.45.2: 🦒

Compare Source

🪲 Bug Fixes
  • Fix internal vector stores quantization config desync by @​Kerollmops in #​6411
    We noticed issues when dumpless upgrading databases containing embedders from versions older than v1.33.1. This version fixes those databases by removing the corrupted embeddings from the impacted indexes.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.45.1...v1.45.2

v1.45.1: 🦒

Compare Source

🪲 Bug Fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.45.0...v1.45.1

v1.45.0: 🦒

Compare Source

Meilisearch v1.45.0 mainly improves indexing performance when changing settings and also improves document fetch performance.

✨ Enhancement
  • Autobatch deletions by filter with additions by @​Kerollmops in #​6389
    While Meilisearch tries to improve indexing speed when users add documents and mix those additions with deletions via a filter, it is still an anti-pattern to interleave both. It is recommended to delete documents by ID whenever possible, as the engine is optimized to merge them, thereby drastically speeding up indexation.
  • Improve settings indexing performance & visibility
    We are introducing support for more settings in the nez settings indexer. If you find any bugs, please report them on GitHub. You can disable the new settings indexer by setting the environment variable like this: MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS=true or use the equivalent dedicated CLI parameter.
    • Support non-extracting parameters by @​Kerollmops in #​6393
      Changing one of the following settings is now directly handled by the new settings indexer: displayed fields, synonyms, the primary key, authorize typos, min word len one and two typos, max values per facet, sort facet values by, pagination max total hits, search cut off, chat, and foreign keys.
    • Support the global facet search by @​Kerollmops in #​6390
      Meilisearch can use the new settings indexer when the settings change the facet search root boolean parameter.
🪲 Bug Fixes
  • Fetching documents no longer blocks the actix worker @​dureuill in #​6402
  • Fix an internal error when changing the binary quantization by @​Kerollmops in #​6396
    We fixed an issue where users were changing the binary-quantized boolean in embedder configurations. The change corrupted the database, making it impossible to change the quantization in the future. Users had to create a binary-quantized embedder from scratch, or they could never change it again.
🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.44.0...v1.45.0

v1.44.0

Compare Source

Meilisearch v1.44.0 adds remote federated facet search, indexing performance improvements, and other improvements and bugfixes. It also contains a couple of breaking changes, detailed below.

Breaking changes

  • When using the network experimental feature, with sharding enabled (leader is not null in the network configuration), POST /indexes/{indexUid}/facet-search calls now default to a remote federated facet search, fetching and merging results from all shards in the network.
  • The timeout for calling an external REST embedder at search time is now tied to the searchCutOffMs defined in the index, rather than fixed.
    • If you observe missing semantic results after upgrading, or HTTP 500 errors for pure semantic search, please increase the value of the search cutoff in the index settings.
    • By @​dureuill in #​6377

🌈 Improvements

Remote facet search

Meilisearch now has the ability to search across all shards of a network during facet search via the existing dedicated facet search route.

  • If you are using the network experimental feature and have a leader defined for your network, remote calls are now the default for calls to POST /indexes/{indexUid}/facet-search
  • The behavior can be controlled explicitly via the new useNetwork parameter of the facet search object.

By @​dureuill in #​6375

Reduce memory usage of the indexing

Reduces allocated memory when computing prefixes and speeds up some operations to avoid unnecessary deserialization.

If you still see high memory usage while the engine is post-processing, we recommend using the --experimental-reduce-indexing-memory-usage option.

By @​Kerollmops in #​6334

Improve GeoJSON indexing performance

This PR upgrades the cellulite library to a version that includes a GeoJSON indexing optimization. With this change, GeoJSON indexing avoids reprocessing documents that were already indexed in dense cells, and only handles newly added documents incrementally as they descend through the recursive cell tree.

By @​YoEight in #​6374

Human-formatted sizes and detailed DB sizes in stats

Adds two new query parameters to GET /indexes/{indexUid}/stats and GET /stats:

  • showInternalDatabaseSizes: boolean, optional, defaults to false. When present, the index stat objects in responses of the stat routes now contain an additional internalDatabaseSizes key, whose value is a dictionary of the internal database names and their current size in the index, like in the stats object of a batch.
  • sizeFormat: human or raw: optional, defaults to raw. When present and set to human, then all database sizes in responses of the stat routes will be returned as a string containing an appropriate unit (MiB, GiB, etc). When missing or set to raw, then the current behavior of expressing the size in bytes as a number is retained.

Note for integrations: The keys in internalDatabaseSizes are subject to change and should not be exposed as a strongly typed object. This is the same as the existing internalDatabaseSizes in batch stats.

Adding showInternalDatabaseSizes to an index stats

 
// curl -X GET "http://localhost:7700/indexes/movies/stats?showInternalDatabaseSizes=true"
{
  "numberOfDocuments": 31944,
  "rawDocumentDbSize": 20594688,
  "avgDocumentSize": 636,
  "isIndexing": false,
  "internalDatabaseSizes": {
    "wordPairProximityDocids": 100827136,
    "documents": 20594688,
    "wordPositionDocids": 18694144,
    "wordFidDocids": 10715136,
    "wordPrefixPositionDocids": 10256384,
    "wordDocids": 9453568,
    "wordPrefixFidDocids": 4603904,
    "wordPrefixDocids": 3424256,
    "main": 1425408,
    "externalDocumentsIds": 999424,
    "fieldIdWordCountDocids": 245760,
    "exactWordPrefixDocids": 16384,
    "celluliteMetadata": 16384
  },
  "numberOfEmbeddings": 0,
  "numberOfEmbeddedDocuments": 0,
  "fieldDistribution": {
    "genres": 31944,
    "id": 31944,
    "overview": 31944,
    "poster": 31944,
    "release_date": 31944,
    "title": 31944
  }
}

Adding showInternalDatabaseSizes and sizeFormat=human to global stats

 
// curl -X GET "http://localhost:7700/stats?showInternalDatabaseSizes=true&sizeFormat=human"
{
  "databaseSize": "351.38 MiB",
  "usedDatabaseSize": "350.64 MiB",
  "lastUpdate": "2026-04-16T13:07:02.74243Z",
  "indexes": {
    "comics": {
      "numberOfDocuments": 31944,
      "rawDocumentDbSize": "23.14 MiB",
      "avgDocumentSize": "751 B",
      "isIndexing": false,
      "internalDatabaseSizes": {
        "wordPairProximityDocids": "98.06 MiB",
        "documents": "23.14 MiB",
        "wordPositionDocids": "17.22 MiB",
        "wordFidDocids": "10.36 MiB",
        "wordPrefixPositionDocids": "9.47 MiB",
        "wordDocids": "8.97 MiB",
        "wordPrefixFidDocids": "4.36 MiB",
        "wordPrefixDocids": "3.27 MiB",
        "main": "1.36 MiB",
        "externalDocumentsIds": "944 KiB",
        "fieldIdWordCountDocids": "240 KiB",
        "exactWordPrefixDocids": "16 KiB",
        "celluliteMetadata": "16 KiB"
      },
      "numberOfEmbeddings": 0,
      "numberOfEmbeddedDocuments": 0,
      "fieldDistribution": {
        "genres": 31944,
        "id": 31944,
        "overview": 31944,
        "poster": 31944,
        "release_date": 31944,
        "title": 31944
      }
    },
    "movies": {
      "numberOfDocuments": 31944,
      "rawDocumentDbSize": "19.64 MiB",
      "avgDocumentSize": "636 B",
      "isIndexing": false,
      "internalDatabaseSizes": {
        "wordPairProximityDocids": "96.16 MiB",
        "documents": "19.64 MiB",
        "wordPositionDocids": "17.83 MiB",
        "wordFidDocids": "10.22 MiB",
        "wordPrefixPositionDocids": "9.78 MiB",
        "wordDocids": "9.02 MiB",
        "wordPrefixFidDocids": "4.39 MiB",
        "wordPrefixDocids": "3.27 MiB",
        "main": "1.36 MiB",
        "externalDocumentsIds": "976 KiB",
        "fieldIdWordCountDocids": "240 KiB",
        "exactWordPrefixDocids": "16 KiB",
        "celluliteMetadata": "16 KiB"
      },
      "numberOfEmbeddings": 0,
      "numberOfEmbeddedDocuments": 0,
      "fieldDistribution": {
        "genres": 31944,
        "id": 31944,
        "overview": 31944,
        "poster": 31944,
        "release_date": 31944,
        "title": 31944
      }
    }
  }
}

The call without any parameters is the same as in previous versions.

 
// curl -X GET "http://localhost:7700/stats"
{
  "databaseSize": 368443392,
  "usedDatabaseSize": 367673344,
  "lastUpdate": "2026-04-16T13:07:02.74243Z",
  "indexes": {
    "comics": {
      "numberOfDocuments": 31944,
      "rawDocumentDbSize": 24264704,
      "avgDocumentSize": 751,
      "isIndexing": false,
      "numberOfEmbeddings": 0,
      "numberOfEmbeddedDocuments": 0,
      "fieldDistribution": {
        "genres": 31944,
        "id": 31944,
        "overview": 31944,
        "poster": 31944,
        "release_date": 31944,
        "title": 31944
      }
    },
    "movies": {
      "numberOfDocuments": 31944,
      "rawDocumentDbSize": 20594688,
      "avgDocumentSize": 636,
      "isIndexing": false,
      "numberOfEmbeddings": 0,
      "numberOfEmbeddedDocuments": 0,
      "fieldDistribution": {
        "genres": 31944,
        "id": 31944,
        "overview": 31944,
        "poster": 31944,
        "release_date": 31944,
        "title": 31944
      }
    }
  }
}

By @​dureuill in #​6338

🦋 Fixes

🔩 Miscellaneous changes

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.43.1...v1.44.0

v1.43.1

Compare Source

Meilisearch v1.43.1 contains a security fix for an authenticated SSRF vulnerability.

No exploitation was found on Meilisearch Cloud. Cloud users are not required to update.

We recommend that self-hosting users upgrade if they allow third parties to configure Meilisearch instances.

We thank Sion Park (@​tldhs1144), who reported the issue and suggested a fix, for improving the security of Meilisearch ❤️

v1.43.0

Compare Source

🌈 Enhancements

New settings indexer

The new settings indexer, a more efficient version of our internal indexer for index settings modifications, now supports filterable, sortable, facet search, and custom (asc/desc) attributes in addition to the already-supported searchable, exact, proximity precision, and embedders.

  • For Meilisearch Cloud users, the new settings indexer is disabled by default and can be enabled on a case-by-case basis for scaling purposes.
  • For OSS users, the new settings indexer can be disabled by setting the MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS to true.

By @​Kerollmops in #​6124

Improve facet search indexing performance

We reduced the time to generate the internal data structures for the facet search to work. We were previously doing a couple of full scans on the internal entries and replaced these with scans on specific entries, only the ones dedicated to the facet searchable fields.

By @​Kerollmops in #​6325

Improve task queue compaction integration

The GET /health route now returns HTTP 500 after a successful task queue compaction, to signal that Meilisearch should be restarted so that tasks can be enqueued again.

For Meilisearch Cloud users, this ensures that compacting the task queue will automatically restart the instance after the compaction.

🦋 Fixes

Fix lexicographic filters on strings

Fixes a bug where string facet values appearing in <, <=, >, >= and IN filters were not normalized before comparison to facet values.

This would cause some values in documents (e.g. 2026-01-01T00:00:00) to appear to be higher than their filter counterpart, due to being normalized (e.g. like 2026-01-01t00:00:00).

Thanks to @​njaard for reporting the issue ❤️

By @​dureuill in #​6340

Fix typo tolerance v1.41 regression

Fixes the WordDelta::added_or_deleted_words function.

By @​Kerollmops in #​6350.

Thanks to @​vladradin99 and @​snurfer0 for reporting the issue in #​6349 and #​6324 ❤️

🔩 Miscellaneous

Thanks again @​gounthar, @​njaard, @​vladradin99 and @​snurfer0 for your contributions ❤️

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.42.1...v1.43.0

v1.42.1: 🦑​

Compare Source

🪲 Bug fixes

Fix issues when using the legacy settings indexer

By @​dureuill and @​ManyTheFish in #​6331

  • When using the experimental feature "multimodal", removing a fragment would cause an internal error in subsequent search requests
  • When using the experimental feature "multimodal", modifying fragments would sometimes cause an internal error at indexing time
  • regenerate: false would be ignored when modifying embedder settings
  • When a nested field was declared as searchable, it would not be indexed if its parents were not declared as searchable

🔩 Miscellaneous

v1.42.0: 🦑​

Compare Source

✨ Enhancement

Support search fallback on remote unavailability

By @​Kerollmops in #​6306

We introduce a new fallback system for the sharding and replication enterprise edition feature, along with a way to determine which remote is available. The engine can avoid machines that are unavailable for a period and resume querying them once they're back online.

The following snippet shows what the /network route looks like now that this PR exposes the remote statuses/availabilities.

"remotes": {
	"prod2": {
	  "url": "http://localhost:7702",
	  "searchApiKey": "mykey",
	  "writeApiKey": "mykey",
	  "status": "available"
	},
	"prod3": {
	  "url": "http://localhost:7703",
	  "searchApiKey": "mykey",
	  "writeApiKey": "mykey",
	  "status": "unavailable"
	}
}

🔬 Experimental: Document join Filtering

By @​ManyTheFish in #​6314

This enhancement extends the Cross-index document hydration introduced in v1.39.0 by allowing the user to filter on the foreign indexes to retrieve the documents.

📓 Note: This implementation doesn't support a remote sharding environment

foreignKeys experimental feature

TheforeignKeys experimental feature must be activated to use the foreign filters:

curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \
  -H 'Content-Type: application/json' \
  --data-binary '{"foreignKeys": true}'
foreignKeys + filter index setting

To be able to use the foreign filters, the related field must be set as a foreignKey and as a filterableAttribute in /indexes/{index_uid}/settings:

{
	// new setting, an array of foreign keys that allows multiple foreign relationships between indexes
	"foreignKeys":  [
		{
			// the path in the JSON document containing foreign document ids
			"fieldName": "actors",
			
			// the UID of the foreign index containing the documents to fetch during hydration
	        "foreignIndexUid": "actors"
		}
	],
	// the actors field must be filterable on equality
	"filterableAttributes": [
		{
	    	"attributePatterns": ["actors"],
	     	"features": {
				"facetSearch": false,
				"filter": {
					"equality": true,
					"comparison": false
				}
			}
		}
	]
}
filtering using the _foreign filter

On the search route, a new _foreign verb has been introduced and should be used as follows:

{
	"q": "<query>",

	// filters on the movie index:
	// genres = action
    // AND
    // the foreign documents from the actor index match:  birthday STARTS WITH \"1958-\" AND popularity >= 3.5
	"filter": "genres = action AND _foreign(actors, birthday STARTS WITH \"1958-\" AND popularity >= 3.5)"
}

Note: nesting foreign filters is not supported and will return an error

Example of usage
Prerequisites
  • Meilisearch running on 127.0.0.1:7700 on the document-join-hydration branch.
Step 1: Enable Foreign Keys Feature
curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \
  -H 'Content-Type: application/json' \
  --data-binary '{"foreignKeys": true}'
Step 2: Create Indexes
Create the actors index
curl -X POST 'http://127.0.0.1:7700/indexes' \
  -H 'Content-Type: application/json' \
  --data-binary '{"uid": "actors", "primaryKey": "id"}'
Create the movies index
curl -X POST 'http://127.0.0.1:7700/indexes' \
  -H 'Content-Type: application/json' \
  --data-binary '{"uid": "movies", "primaryKey": "id"}'
Step 3: Add Documents to the actors Index
curl -X POST 'http://127.0.0.1:7700/indexes/actors/documents' \
  -H 'Content-Type: application/json' \
  --data-binary '[
  {"id": 1, "name": "Tom", "familyName": "Hanks", "birthDate": "1956-07-09"},
  {"id": 2, "name": "Meryl", "familyName": "Streep", "birthDate": "1949-06-22"},
  {"id": 3, "name": "Leonardo", "familyName": "DiCaprio", "birthDate": "1974-11-11"},
  {"id": 4, "name": "Emma", "familyName": "Watson", "birthDate": "1990-04-15"}
]'
Step 4: Add Documents to the movies Index
curl -X POST 'http://127.0.0.1:7700/indexes/movies/documents' \
  -H 'Content-Type: application/json' \
  --data-binary '[
  {"id": 1, "title": "Forrest Gump", "description": "The presidencies of Kennedy and Johnson, the Vietnam War, the Watergate scandal and other historical events unfold from the perspective of an Alabama man with an IQ of 75.", "actors": [1]},
  {"id": 2, "title": "The Devil Wears Prada", "description": "A smart but sensible new graduate lands a job as an assistant to Miranda Priestly, the demanding editor-in-chief of a high fashion magazine.", "actors": [2, 4]},
  {"id": 3, "title": "Inception", "description": "A thief who steals corporate secrets through the use of dream-sharing technology is given the inverse task of planting an idea into the mind of a C.E.O.", "actors": [3]},
  {"id": 4, "title": "Cast Away", "description": "A FedEx executive undergoes a physical and emotional transformation after crash landing on a deserted island.", "actors": [1]}
]'
Step 5: Configure Foreign Keys on the movies Index
curl -X PATCH 'http://127.0.0.1:7700/indexes/movies/settings' \
  -H 'Content-Type: application/json' \
  --data-binary '{"foreignKeys": [{"fieldName": "actors", "foreignIndexUid": "actors"}], "filterableAttributes": [{"attributePatterns": ["actors"],"features": {"facetSearch": false,"filter": {"equality": true,"comparison": false}}}]}'
Step 6: Configure filterable on the actors Index
curl -X PATCH 'http://127.0.0.1:7700/indexes/actors/settings' \
  -H 'Content-Type: application/json' \
  --data-binary '{"filterableAttributes": [{"attributePatterns": ["birthDate"],"features": {"facetSearch": false,"filter": {"equality": true,"comparison": false}}}]}'
Step 7: Perform a Federated Search
curl -X POST 'http://127.0.0.1:7700/multi-search' \
  -H 'Content-Type: application/json' \
  --data-binary '{
  "queries": [
    {
      "indexUid": "movies",
      "q": "Forrest",
      "filter": "_foreign(actors, birthDate = \"1956-07-09\")"
    }
  ],
  "federation": {
    "limit": 20,
    "offset": 0
  }
}'
Expected Result

The federated search should return movie documents with the actors array automatically hydrated with full actor objects instead of just IDs:

{
  "hits": [
    {
      "id": 1,
      "title": "Forrest Gump",
      "description": "...",
      "actors": [
        {
          "id": 1,
          "name": "Tom",
          "familyName": "Hanks",
          "birthDate": "1956-07-09"
        }
      ],
      "_federation": {
        "indexUid": "movies",
        "queriesPosition": 0,
        "weightedRankingScore": 0.9848484848484849
      }
    }
  ],
  "processingTimeMs": 208,
  "limit": 20,
  "offset": 0,
  "estimatedTotalHits": 1
}

🪲 Bug fixes

  • Fix a race condition when writing network by @​Kerollmops in #​6300

    We fixed a race condition in network topology changes that could cause errors and prevent documents from being correctly indexed. Additionally, we fixed a bug in the networkTopologyChange task batching that was causing it to batch too many task types. We made sure it only batches import tasks, and only those, to avoid out-of-order task processing.

  • Throw document template errors when updating the chat settings by @​Kerollmops in #​6321

    We fixed an issue that prevented the engine from explicitly showing the possible document template errors users could encounter when updating the template in the chat settings. The engine now correctly checks for and throws template errors when they are detected.

  • Fix: Update Index tasks will be properly forwarded to remote nodes by @​dureuill in #​6299

  • Fix action mistake on the chat completions route by @​Kerollmops in #​6290

🔩 Miscellaneous

v1.41.0: 🏈

Compare Source

✨ Enhancement

  • Support dynamic search rules with pinning by @​YoEight in #​6182
    Introduce the Dynamic Search Rules (DSR) experimental feature, making it easy to promote the right content for the right searches with flexible, condition-based pinning. In this first version, rules can be triggered by query-based conditions such as empty queries or literal substring matches, as well as time windows. Multiple documents can be pinned in a defined order, and pins still work with filtering, pagination, facet distribution, hybrid search, and federated search. This feature is behind the dynamicSearchRules experimental feature flag.

    Rules can be created or updated with PATCH /dynamic-search-rules/{uid} and removed with DELETE /dynamic-search-rules/{uid}. In this first version, a rule can define query- or time-based conditions and pin specific documents at fixed positions in the results list.

    Example of rule creation/update 
      // PATCH /dynamic-search-rules/featured-wireless-headphones
  {
    "description": "Promote featured products for wireless headphone searches",
    "active": true,
    "conditions": [
      { "scope": "query", "contains": "headphone" }
    ],
    "actions": [
      {
        "selector": { "indexUid": "products", "id": "featured-headphones-001" },
        "action": { "type": "pin", "position": 0 }
      },
      {
        "selector": { "indexUid": "products", "id": "featured-headphones-002" },
        "action": { "type": "pin", "position": 1 }
      }
    ]
  }

  • Default to useNetwork: true in sharded instances by @​dureuill in #​6278

    This release contains breaking changes for users of the network experimental feature.

    Search requests now use the network by default when (replicated) sharding is enabled
    § Breaking changes

    When network.leader is set in the instance, useNetwork now defaults to true in search requests when omitted.

    So, when a network is configured, the following:

    Search request without an explicit useNetwork 
    // POST /indexes/movies/search
{
  "q": "Batman dark knight returns 1",
  "filter": "genres IN [Action, Adventure]",
  "facets": ["genres"],
  "limit": 5
  // No `useNetwork` is passed
}

    is now equivalent to a federated search over multiples remotes so that all shards in the network are covered exactly once.

    Equivalent federated search request 
    // POST /multi-search
{
    "federation": {
        "limit": 5,
        "facetsByIndex": {
            "movies": [
                "genres"
            ]
        },
        "merge": {}
    },
    // assuming 3 remotes 0, 1, 2 and 3 shards a, b, c such that
    // 0 owns a, b
    // 1 owns b, c
    // 2 owns c, a
    "queries": [
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "0"
            },
            "q": "Batman dark knight returns 1",
            "filter": ["genres IN [Action, Adventure]", "_shard = a"]
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "0" // useNetwork picked remote 0 for both shard a and b
            },
            "q": "Batman dark knight returns 1",
		     "filter": ["genres IN [Action, Adventure]", "_shard = b"]
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "2"
            },
            "q": "Batman dark knight returns 1",
		     "filter": ["genres IN [Action, Adventure]", "_shard = c"]
        }
    ]
}

    Responding with documents from all the shards:

    Response 
    {
  "hits": [
    {
      "id": 123025,
      "title": "Batman: The Dark Knight Returns, Part 1",
      "overview": "Batman has not been seen for ten years. A new breed of criminal ravages Gotham City, forcing 55-year-old Bruce Wayne back into the cape and cowl. But, does he still have what it takes to fight crime in a new era?",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/kkjTbwV1Xnj8wBL52PjOcXzTbnb.jpg",
      "release_date": 1345507200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.9894586894586894,
        "remote": "2"
      }
    },
    {
      "id": 142061,
      "title": "Batman: The Dark Knight Returns, Part 2",
      "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city.  Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg",
      "release_date": 1357171200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9894558963186414,
        "remote": "0"
      }
    },
    {
      "id": 16234,
      "title": "Batman Beyond: Return of the Joker",
      "overview": "The Joker is back with a vengeance, and Gotham's newest Dark Knight needs answers as he stands alone to face Gotham's most infamous Clown Prince of Crime.",
      "genres": [
        "Animation",
        "Family",
        "Action",
        "Science Fiction"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/7RlBs0An83fqAuKfwH5gKMcqgMc.jpg",
      "release_date": 976579200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9427964918160996,
        "remote": "0"
      }
    },
    {
      "id": 155,
      "title": "The Dark Knight",
      "overview": "Batman raises the stakes in his war on crime. With the help of Lt. Jim Gordon and District Attorney Harvey Dent, Batman sets out to dismantle the remaining criminal organizations that plague the streets. The partnership proves to be effective, but they soon find themselves prey to a reign of chaos unleashed by a rising criminal mastermind known to the terrified citizens of Gotham as the Joker.",
      "genres": [
        "Drama",
        "Action",
        "Crime",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/qJ2tW6WMUDux911r6m7haRef0WH.jpg",
      "release_date": 1216166400,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.5784178187403994,
        "remote": "0"
      }
    },
    {
      "id": 49026,
      "title": "The Dark Knight Rises",
      "overview": "Following the death of District Attorney Harvey Dent, Batman assumes responsibility for Dent's crimes to protect the late attorney's reputation and is subsequently hunted by the Gotham City Police Department. Eight years later, Batman encounters the mysterious Selina Kyle and the villainous Bane, a new terrorist leader who overwhelms Gotham's finest. The Dark Knight resurfaces to protect a city that has branded him an enemy.",
      "genres": [
        "Action",
        "Crime",
        "Drama",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/vzvKcPQ4o7TjWeGIn0aGC9FeVNu.jpg",
      "release_date": 1342396800,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.5772657450076805,
        "remote": "2"
      }
    }
  ],
  "query": "Batman dark knight returns 1",
  "processingTimeMs": 173,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 47,
  "facetDistribution": {
    "genres": {
      "Action": 46,
      "Adventure": 15,
      "Animation": 34,
      "Comedy": 3,
      "Crime": 14,
      "Drama": 6,
      "Family": 15,
      "Fantasy": 8,
      "Horror": 1,
      "Mystery": 4,
      "Romance": 1,
      "Science Fiction": 14,
      "TV Movie": 4,
      "Thriller": 4,
      "Western": 1
    }
  },
  "facetStats": {},
  "requestUid": "019bbcf4-a609-7701-8d82-d370611adfb3",
  "remoteErrors": {}
}

    This change allows to naturally query all the documents in a sharded context.
    When network.leader is not present (in particular, when no network was defined), then the behavior is identical to previous versions.

  • useNetwork picks local instance if it owns the shard by @​dureuill in #​6287
    To prevent unnecessary network activity, when deciding which remote to ask for a shard in a search over the network, Meilisearch will now always pick the local instance if it owns the shard.

  • More efficient FST building by @​Kerollmops in #​6279
    It improves the construction of the word FST (word dictionary) by removing the need for a full scan of the word docids database. This should drastically improve the database's performance when inserting a large number of documents, even when inserting only a few.

🪲 Bug fixes
🔩 Miscellaneous

New Contributors

v1.40.0: 🦈

Compare Source

This release introduced support for the distinct attribute in federated search, enabling cross-index distinct attributes with facet distribution support. Additionally, significant performance improvements were delivered, including faster federated search (approximately 100ms faster), optimized JSON document generation for better handling of large documents and a much better memory usage for large workloads.

✨ Enhancement

  • Support distinct in federated search by @​dureuill in #​6214

    The distinct attribute can now be passed to the federation object in federated search to apply a global, cross-index and cross-remote distinct computation to the results.

    Example of a federated search request with distinct 
    {
  "federation": {
    "distinct": "genres", // ✨ NEW
    "facetsByIndex": { // recovering facet distribution is also supported with distinct
      "comics": [
        "genres"
      ],
      "movies": [
        "genres"
      ]
    },
    "mergeFacets": {} // merging facet distributions is also supported with distinct
  },
  "queries": [
    {
      "indexUid": "comics",
      "q": "batman",
      "attributesToRetrieve": ["title", "genres"],
      "useNetwork": true // distinct is also supported with network queries
    },
    {
      "indexUid": "movies",
      "q": "superman",
      "attributesToRetrieve": ["title", "genres"],
      "useNetwork": true
    }
  ]
}
    Sample response to a federated search request with distinct 
    {
  "hits": [
    {
      "title": "Batman",
      "genres": [
        "Family",
        "Adventure",
        "Comedy",
        "Science Fiction",
        "Crime"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 1.0,
        "remote": "ms2"
      }
    },
    {
      "title": "Batman",
      "genres": [
        "Fantasy",
        "Action"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 1.0,
        "remote": "ms1"
      }
    },
    {
      "title": "Batman & Bill",
      "genres": [
        "Documentary"
      ],
      "_federation": {
        "indexUid": "comics",
        "queriesPosition": 0,
        "weightedRankingScore": 0.9848484848484848,
        "remote": "ms1"
      }
    },
    {
      "title": "Superman: Red Son",
      "genres": [],
      "_federation": {
        "indexUid": "movies",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9848484848484849,
        "remote": "ms0"
      }
    },
    {
      "title": "Superman, Spider-Man or Batman",
      "genres": [
        "Drama"
      ],
      "_federation": {
        "indexUid": "movies",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9848484848484849,
        "remote": "ms0"
      }
    }
  ],
  "processingTimeMs": 15,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 11,
  "facetDistribution": {
    "genres": {
      "Action": 1,
      "Adventure": 1,
      "Comedy": 3,
      "Crime": 2,
      "Documentary": 1,
      "Drama": 1,
      "Family": 1,
      "Fantasy": 1,
      "Horror": 2,
      "Romance": 1,
      "Science Fiction": 1,
      "Thriller": 1,
      "Western": 1
    }
  },
  "facetStats": {},
  "requestUid": "019d05c7-ea65-77a1-8274-22a8ba9e26db",
  "remoteErrors": {}
}

    Note the following to apply the distinct attribute at the federation level:

    1. Applying distinct at the query level at the same time as the federation level is disallowed and will return a HTTP 400 error.
    2. The chosen distinct field will apply to all remotes and indexes, so it must be a filterable attribute for all participating remotes and indexes.
    3. While Meilisearch attempts to compute the most accurate facet distribution, in distributed contexts this cannot be guaranteed as the distinct algorithm is not applied on all of the remote documents.

  • Improve performance of federated search by @​dureuill in #​6229

    Improves performance of federated search: about 100ms faster for all requests. Improves reliability of the HTTP server: the server will no longer be blocked when too many federated search requests are being processed.

  • Optimize the generation of JSON documents by @​Kerollmops in #​6257

    Addresses performance issues that users might encounter when requesting large documents. Additionally, performance is enhanced when users request only a small subset of fields from large documents.

  • Use the latest version of mimalloc to improve memory usage by @​Kerollmops in #​6201

    Updates mimalloc from v2 to v3, improving memory sharing between threads and significantly reducing memory usage on large workloads. It also overrides the allocator to use mimalloc at linking time, allowing LMDB, Meilisearch, and other C libraries to share their allocations for better overall memory efficiency. @​Kerollmops wrote a blog post about the story behind this improvement.

  • Add POST /tasks/compact for task queue compaction by @​YoEight in #​6193

    Compacts the task queue database and reclaim space so new tasks can keep being enqueued, without deleting existing tasks. This feature is behind the taskQueueCompactionRoute experimental feature flag.

[!WARNING]
Once task queue compaction completes, all write operations are blocked until the server is restarted.

🔐 Security
  • Bump rustls-webpki from 0.103.8 to 0.103.10 in #​6273
  • Bump tar from 0.4.44 to 0.4.45 in #​6271
  • Bump actix-web-lab from 0.24.3 to 0.26.0 in #​6218
  • Bump quinn-proto from 0.11.13 to 0.11.14 in #​6217
🪲 Bug fixes
🔩 Miscellaneous

New Contributors

v1.39.0: 🐳​

Compare Source

What's Changed

✨ Enhancement

🔬 Cross-index document hydration

Add a new ForeignKeys setting allowing to hydrate documents with documents coming from other indexes.

📓 Note: This implementation doesn't support a remote sharding environment

foreignKeys experimental feature

A new experimental feature, foreignKeys, has been added to the /experimental-feature route that must be set to true to activate the hydration.

curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \
  -H 'Content-Type: application/json' \
  --data-binary '{"foreignKeys": true}'
foreignKeys index setting

A new index setting, foreignKeys, has been added to the /indexes/{index_uid}/settings:

// new setting, an array of foreign keys that allows multiple foreign relationships between indexes
"foreignKeys":  [
	{
		// the path in the JSON document containing foreign document ids
		"fieldName": "actors",
		
		// the UID of the foreign index containing the documents to fetch during hydration
        "foreignIndexUid": "actors"
	}
]
Example

With this new feature, a document shaped as follows:

{
  "id": 1,
  "title": "Forrest Gump",
  // Document IDs in foreign index
  "actors": [
    1
  ]
}

Will be hydrated as follows in a search response:

{
  "id": 1,
  "title": "Forrest Gump",
  "actors": [
	{
	  "id": 1,
	  "name": "Tom",
	  "familyName": "Hanks",
	  "birthDate": "1956-07-09"
	}
  ]
}

By @​ManyTheFish in #​6047

Disable proxy response buffering on Server-Sent Events (SSE)

Add X-Accel-Buffering: no on POST /chats/{workspace_uid}/chat/completions when the streaming mode is activated.
By @​YoEight in #​6228

🪲 Bug fixes

  • Fix a memory leak in the indexation pipeline by @​Kerollmops in #​6212

    We fixed an important memory leak caused by an invalid use of bumpalo. If you've seen Meilisearch using more and more memory over time, this issue is no longer visible in the latest version. If you want to read more about the bumpalo-trap we felt in, here is a good summary. It looks like this leak was introduced in v1.12, so approximately a year ago...

  • Avoid losing tasks by applying deltas on the wtxn view by @​Kerollmops in #​6222

    We addressed a small performance regression introduced in v1.38.1 that affected sending updates to the engine during task deletion. We've restored the task deletion performance to match v1.38.0 levels and ensured no race conditions occur while still allowing updates during deletion.

🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.38.0...v1.39.0

v1.38.2: 🐍

Compare Source

Meilisearch v1.38.2 fixes a regression introduced in Meilisearch v1.38.0 where Meilisearch could sometimes stop processing tasks after an automatic task queue cleanup performed while more tasks where being added.

We recommend that all users in v1.38.0 and v1.38.1 migrate to v1.38.2.

Note that the dumpless upgrade process can take up to one minute before the HTTP server becomes available when migrating from a previous v1.38 version.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.38.1...v1.38.2

v1.38.1: 🐍

Compare Source

Meilisearch v1.38.1 fixes a regression we have seen in task processing, which caused the engine to stop processing tasks.

🪲 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.38.0...v1.38.1

v1.38.0: 🐍

Compare Source

Meilisearch v1.38 drastically improves indexing performance for embeddings, cleans up the task queue of orphan tasks and batches, ensures they are correctly deleted now, fixes issues users may encounter with OpenAI or VoyageAI when generating embeddings, and improves the tooling for generating routes in the documentation.

✨ Enhancement
  • Embeddings: Use the latest version of hannoy with improved performances by @​Kerollmops in #​6184
    We drastically reduced embedding indexing time by eliminating full database scans. It is more efficient to add a couple of embeddings to a large database now.
  • Tasks: Optimize and fix task deletion by @​Mubelotix and @​kerollmops in #​5828
🪲 Bug fixes
  • Embedders: Fix the intermittent connection reset by peer errors when embedding documents or search queries using a remote embedder. By @​dureuill in #​6191
🔩 Miscellaneous
  • Enforce that routes appear in the reference documentation by @​dureuill and @​manythefish in #​6200
    The reference API is now generated from the source code, but it used to miss some actix-declared routes. It is now mandatory to attach a route when using the newly-provided routes::routes and routes::path macros, which ensures the route is added to the reference. Please refer to the documentation of the individual macros and the many examples throughout the codebase for more details.
  • Chore: remove verbose debug log on list documents by @​StephaneRob in #​6198
  • Add guide to CONTRIBUTING.md to test doc locally by @​curquiza in #​6180
  • Docs: capitalize LangChain and MCP in README by @​24f1000637 in #​6183
  • Docs: improve documentation of the parameters of the search route by @​curquiza in #​6194
New Contributors

v1.37.0

Compare Source

[!IMPORTANT]
This release contains breaking changes for users of the network experimental feature.

Meilisearch v1.37 introduces replicated sharding, removes the vectorStoreSetting experimental feature, stabilizes our new vector store for best performance, adds a security fix and miscellaneous improvements.

✨ Improvements

§ Replicated sharding

[!NOTE]
Replicated sharding requires Meilisearch Enterprise Edition (EE).

  • Users of Meilisearch Cloud, please contact support if you need replicated sharding.
  • Users of the Community Edition, please contact the sales if you want to use replicated sharding in production.
§ Breaking changes
  • network objects sent to the PATCH /network route must now contain at least one shard object containing at least one remote when leader is not null.

Existing databases will be migrated automatically when upgraded with --experimental-dumpless-upgrade when leader is not null, such that for each remote:

  1. A shard with the same name as the remote is created
  2. This shard has exactly one remote in its remotes list: the remote with the same name as the shard.

This change will not cause any document to be resharded.

To be able to upgrade without resharding, the migration uses the same name for remotes and for shards. However, in new configurations, we recommend using different names for shards and remotes.

Example of migration

For instance, the following network object:

{
  "leader": "ms-00",
  "self": "ms-01",
  "remotes": {
    "ms-00": { /* .. */ },
    "ms-01": { /* .. */ }
  }
}

is converted to:

{
  "leader": "ms-00",
  "self": "ms-01",
  "remotes": {
    "ms-00": { /* .. */ },
    "ms-01": { /* .. */ }
  },
  "shards": {  // ✨ NEW
    "ms-00": {  // shard named like the remote
      "remotes": ["ms-00"] // is owned by the remote
    },
    "ms-01": {
      "remotes": ["ms-01"]
    }
  }
}
Addition of network.shards

The network object for routes PATCH /network and GET /network now contains the new field shards, which is an object whose values are shard objects, and keys the name of each shard.

Each shard object contains a single field remotes, which is an array of strings, each string representing the name of an existing remote.

Convenience fields

The shard objects in PATCH /network contain the additional fields addRemotes and removeRemotes meant for convenience:

  • pass an array of remote names to shard.addRemotes to add these remotes to the list of remotes of a shard.
  • pass an array of remote names to shard.removeRemotes to remove these remotes from the list of remotes of a shard.
  • if present and non-null, shard.remotes will completely override the existing list of remotes for a shard.
  • if several of these options are present and non-null, then the order of application is shard.remotes, then shard.addRemotes, then shard.removeShards.
Adding a new shard with some remotes 
// PATCH /network
{
  // assuming that remotes `ms-0`, `ms-1`, `ms-2` where sent in a previous call to PATCH /network
  "shards": {
    "s-a": { // new shard
      "remotes": ["ms-0", "ms-1"]
    }
  }
}

Remotes ms-0 and ms-1 own the new shard s-a.

Fully overriding the list of remotes owning a shard 
// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-0` and `ms-1`
  "shards": {
    "s-a": {
      "remotes": ["ms-2"]
    }
  }
}

ms-2 is now the sole owner of s-a, replacing ms-0 and ms-1.

Adding a remote without overriding the list of remotes owning a shard 
// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-2`
  "shards": {
    "s-a": {
      "addRemotes": ["ms-0"]
    }
  }
}

ms-0 and ms-2 are now the owners of s-a.

Removing a remote without overriding the list of remotes owning a shard 
// PATCH /network
{
  // assuming remotes `ms-0`, `ms-1`, `ms-2`
  // assuming shard `s-a`, owned by `ms-0` and `ms-2`
  "shards": {
    "s-a": {
      "removeRemotes": ["ms-2"]
    }
  }
}

ms-0 is now the sole owner of s-a.

Entirely removing a shard from the list of shards

Set the shard to null:

// PATCH /network
{
  "shards": {
    "s-a": null
  }
}

Or set its remotes list to the empty list:

// PATCH /network
{
  "shards": {
    "s-a": {
      "remotes": []
    }
  }
}
network.shards validity

When network.leader is not null, each shard object in network.shards must:

  1. Only contain remotes that exist in the list of remotes.
  2. Contain at least one remote.

Additionally, network.shards must contain at least one shard.

Failure to meet any of these conditions will cause the PATCH /network route to respond with 400 invalid_network_shards.

Change in sharding logic

Documents are now sharded according to the list of shards declared in the network rather than the list of remotes. All remotes owning a shard will process the documents that belong to this shard, allowing for replication.

Example of replication

The following configuration defines 3 remotes 0, 1 and 2, and 3 shards A, B, C, such that each remote owns two shards, achieving replication (losing one remote does not lose any document).

{
  "leader": "0",
  "self": "0",
  "remotes": {
    "0": { /* .. */ },
    "1": { /* .. */ },
    "2": { /* .. */ }
  },
  "shards": {
    "A": {
      "remotes": ["0", "1"]
    },
    "B": {
      "remotes": ["1", "2"]
    },
    "C": {
      "remotes": ["2", "0"]
    }
  }
}
  • Full replication is supported by having all remotes own all the shards.
  • Unbalanced replication is supported by having some remotes own more shards than other remotes.
  • "Watcher" remotes are supported by having remotes that own no shards. Watcher remotes are not very useful in this release, and might be upgraded in a future release, so that they keep all documents without indexing them, allowing to "respawn" shards for other remotes.
useNetwork takes network.shards into account

When useNetwork: true is passed to a search query, it is expanded to multiple queries such that each shard declared in network.shards appears exactly once, associated with a remote that owns that shard.

This ensures that there is no missing or duplicate documents in the results.

_shard filters

When the network experimental feature is enabled, then it becomes possible to filter documents depending on the shard they belong to.

Given s-a and s-b the names of two shards declared in network.shards, then:

  • _shard = "s-a" in a filter parameter to the search or documents fetch will return the documents that belong to s-a.
  • _shard != "s-a" will return the documents that do not belong to s-a
  • _shard IN ["s-a", "s-b"] will return the documents that belong to s-a or to s-b.

You can use these new filters in manual remote federated search to create a partitioning over all shards in the network.

[!IMPORTANT]
To avoid duplicate or missing documents in results, for manually crafted remote federated search requests, all shards should appear in exactly one query.

[!TIP]
Search requests built with useNetwork: true already build a correct partitioning over shards. They should be preferred to manually crafted remote federated search requests in replicated sharding scenarios.

Update instructions

When updating your Meilisearch network using dumpless upgrade, please observe the following guidelines:

  1. Do not call the PATCH /network route until all remotes of the network are finished updating
  2. If using the search routes with useNetwork: true, call them on un-updated remotes. Calling it on already updated remotes will cause un-updated remotes to fail the search as they don't know about the _shard filters.

By @​dureuill in #​6128

§ Remove vectorStoreSetting experimental feature

The new HNSW vector store (hannoy) has been stabilized and is now the only supported vector store in Meilisearch.

As a result, updating to v1.37.0 will migrate all remaining legacy vector store indexes (using arroy) to hannoy, and the vectorStoreSetting experimental feature is no longer available.

By @​Kerollmops in #​6176

Improve indexing performance for embeddings

We removed a computationally expensive step from vector indexing.

On a DB with 20M documents, this removes 300s per indexing batch of 1100s.

By @​Kerollmops in #​6175

§ 🔒 Security

  • Bump mini-dashboard (local web interface) which
    • now stores API key in RAM instead of in the localStorage
    • bumps dependencies with potential security vulnerabilities

By @​Strift and @​curquiza in #​6186 and #​6172

§ 🔩 Miscellaneous

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.36.0...v1.37.0

v1.36.0: 🐙

Compare Source

Version v1.36.0 introduces an exciting update to the ranking rules to improve the engine's relevance. It's actually the first time we've made such a change since v1.0, and we're really happy about this improvement!

✨ Enhancement

  • Introduce the attributeRank and wordPosition criteria by @​Kerollmops in #​6154, #​6155, and #​6164

    We released two new ranking rules that Meilisearch had already been using internally for the attribute one, which is basically both ranking rules applied one after the other:

    • attributeRank: A document is considered better if the query words match in a higher searchable attribute. It ignores the position of the query words in this attribute.
    • wordPosition: A document is considered better if the query words match closer to the beginning of an attribute. The attribute rank is ignored by this rule.

  • We continue our policy of migrating everyone to use a homemade HNSW by introducing a new dumpless upgrade step that migrates index uses the old annoy vector store to the new Hannoy one. Changing the vector store backend affects the ranking score. This step can take a couple of minutes when the number of embeddings is high, and we recommend changing the vector store backend beforehand to gain more control if needed. To do so, you must enable the vectorStoreSetting experimental feature and set the vectorStore root setting to experimental.

🪲 Bug fixes
  • Fix search failing when using attributesToSearchOn on an empty index by @​zen-zap in #​5944
🔒 Security
🔩 Miscellaneous

[!WARNING]
Breaking change: the meilisearch-openapi-mintlify.json file will not be available in the release assets anymore. If you were using it, please refer to the one that is now available in our public documentation repository.

❤️ Thanks to @​zen-zap for contributing to this release!

v1.35.1

Compare Source

🦋 Bug fixes

Meilisearch v1.35.1 fixes a possible task database corruption issue that would occur when using the S3 streaming snapshot method.

  • Users of the Community Edition do not need to upgrade as this feature is Enterprise Edition only
  • Affected users of the Cloud have been contacted.

Details

While snapshotting the task database, sending a task to Meilisearch could corrupt it. Index DBs were not affected, so manually rebuilding the task database fixes the corruption.

By @​dureuill in #​6160

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.35.0...v1.35.1

v1.35.0

Compare Source

Meilisearch v1.35.0 contains improvements to the observability of the search performance, a breaking change to the recently introduced POST /indexes/<index_uid>/fields route, and other bugfixes and improvements.

🌈 Improvements

Observe the search performance

The search routes accept a new field named showPerformanceDetails. When set to true, the search response contains a performance trace, allowing the user to better
understand what takes time during a search query.

impacted routes:

  • POST /indexes/<index_uid>/search
  • GET /indexes/<index_uid>/search
  • POST /multi-search
  • POST /indexes/<index_uid>/similar
  • GET /indexes/<index_uid>/similar
Search

routes: POST /indexes/<index_uid>/search and GET /indexes/<index_uid>/search

Request

new request parameters:

  • showPerformanceDetails: true/false (boolean)
example 
{
	"q": "glass",
	"showPerformanceDetails": true
}
Response

new response field:

  • performanceDetails: {"<span>": "<human_duration>", .. } (map)
example 
{
	"hits": [
		// hits ..
	],
	"query": "glass",
	"processingTimeMs": 5,
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 1,
	"requestUid": "<uuid>",
	"performanceDetails": {
		"wait for permit": "295.29µs",
		"search > tokenize": "436.67µs",
		"search > resolve universe": "649.00µs",
		"search > keyword search": "515.71µs",
		"search > format": "288.54µs",
		"search": "3.56ms"
	}
}
Multi-search

route: POST /multi-search

Request

new request parameters:

  • queries.showPerformanceDetails: true/false (boolean)
example 
"queries": [
	{
		"indexUid": "<index_uid>",
		"q": "glass",
		"showPerformanceDetails": true
	}
]
Response

new response field:

  • results.performanceDetails: {"<span>": "<human_duration>", .. } (map)
example 
{
	"results": [
		{
			"indexUid": "<index_uid>",
			"hits": [
				// hits ..
			],
			"query": "glass",
			"processingTimeMs": 5,
			"limit": 20,
			"offset": 0,
			"estimatedTotalHits": 1,
			"requestUid": "<uuid>",
			"performanceDetails": {
				"wait for permit": "295.29µs",
				"search > tokenize": "436.67µs",
				"search > resolve universe": "649.00µs",
				"search > keyword search": "515.71µs",
				"search > format": "288.54µs",
				"search": "3.56ms"
			}
		}
	]
}
Federated Search

route: POST /multi-search

Request

new request parameters:

  • federation.showPerformanceDetails: true/false (boolean)
example 
{
	"federation": { "showPerformanceDetails": true },
	"queries": [
		{
			"indexUid": "<index_uid>",
			"q": "glass"
		}
	]
}
Response

new response field:

  • performanceDetails: {"<span>": "<human_duration>", .. } (map)
example 
{
	"hits": [
		// hits ..
	],
	"query": "glass",
	"processingTimeMs": 5,
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 1,
	"requestUid": "<uuid>",
	"performanceDetails": {
		"wait for permit": "213.83µs",
		"search > tokenize": "171.67µs",
		"search > resolve universe": "257.63µs",
		"search > keyword search": "577.71µs",
		"search > format": "114.96µs",
		"search > federation > wait for remote results": "62.71µs",
		"search > federation > merge results": "120.04µs",
		"search > federation > merge facets": "53.42µs",
		"search > federation": "237.04µs",
		"search": "289.08ms"
	}
}
Similar

routes: POST /indexes/<index_uid>/similar and GET /indexes/<index_uid>/similar

Request

new request parameters:

  • showPerformanceDetails: true/false (boolean)
example 
{
	"id": 143,
	"embedder": "manual",
	"showPerformanceDetails": true
}
Response

new response field:

  • performanceDetails: {"<span>": "<human_duration>", .. } (map)
example 
{
	"hits": [
		// hits ..
	],
	"id": "143",
	"processingTimeMs": "[duration]",
	"limit": 20,
	"offset": 0,
	"estimatedTotalHits": 4,
	"performanceDetails": {
		"search > format": "244.92µs",
		"search": "1.25ms"
	}
}

By @​ManyTheFish in #​6132

Stabilize multithreaded post-processing of facets and prefixes

Multithreaded post-processing of facets and prefixes speeds-up indexing on multi-core machines.

Before v1.35.0, it could be disabled with an experimental feature.

Meilisearch v1.35.0 removes that experimental feature, resulting in the multithreaded post-processing being always enabled.

Cloud users upgrading to v1.35.0 will benefit from the speed-up.

By @​ManyTheFish in #​6130

🦋 Fixes

Breaking change: return pagination fields in POST /indexes/<index_uid>/fields route

[!WARNING]
Breaking change: The POST /indexes/<index_uid>/fields route now returns an object containing the results, offset, limit, and total fields instead of returning an array of results. This change allows to know how many fields match a given filter

Example: before/after

Before:

[
  // fields ..
]

After:

{
  "results": [
    // [fields .. ]
  ],
  "offset": 0,
  "limit": 20,
  "total": 0
}

By @​ManyTheFish in #​6126

POST /indexes/<index_uid>/fields: Fix pattern filtering when a parent field was matching a child pattern: title was matching the pattern title.to*.

Example: before/after

For the following request:

{
  "filter": {
    "attributePatterns": [
      "title.en"
    ]
  }
}

Before Response, title field is returned:

{
  "results": [
    {
      "name": "title",
      //metadata...
    },
    
  ],
  "offset": 0,
  "limit": 20,
  "total": 1
}

After Response, nothing returned:

{
  "results": [],
  "offset": 0,
  "limit": 20,
  "total": 0
}

By @​ManyTheFish, also in #​6126

🐛 Other fixes

🔩 Miscellaneous

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.34.3...v1.35.0

v1.34.3

Compare Source

🐛 Bug Fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.34.2...v1.34.3

v1.34.2

Compare Source

This patch fixes an accidental breaking change in v1.34.1 where Meilisearch would not start with a configuration file if experimental_allowed_ip_networks was not defined.

  • Meilisearch Cloud users do not need to update as they were not affected by this regression
  • We recommend that OSS users upgrade to v1.34.2

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.34.1...v1.34.2

v1.34.1

Compare Source

In Meilisearch v1.34.1, we released a security fix that affect web queries initiated by Meilisearch.

🔐 Security

  • Cloud users: no action is needed. We found no evidence of exploitation on Meilisearch Cloud and the Cloud is protected at the infrastructure level.
  • Open-source users: if you allow untrusted users to configure webhooks, embedders or network of machines, we recommend you update to Meilisearch v1.34.1

In Meilisearch versions v1.8 to v1.34.0, a user with an API key with write permissions to the configuration of the Meilisearch instance could set up Meilisearch to send POST or GET requests to domains and IPs local to the private network of the Meilisearch instance, effectively bypassing the firewall. The vulnerability has not yet been assigned a CVE number; it has CVE Request 1975471 for CVE ID.

Meilisearch v1.34.1 fixes the vulnerability by forbidding Meilisearch from making any requests to a host resolving to a non-global IP, in the sense of the IANA IPv4 Special-Purpose Address Registry or the IANA IPv6 Special-Purpose Address Registry. If you need this functionality in your Meilisearch instance, you can set private IP networks as allowed with the --experimental-allowed-ip-networks parameter after reviewing the security implications.

This is a breaking change, which is allowed for security reasons.

Allowing non-global IP networks

The --experimental-allowed-ip-networks CLI flag and the MEILI_EXPERIMENTAL_ALLOWED_IP_NETWORKS environment variable control the behavior of Meilisearch with regards to non-global IP networks, with the CLI flag taking precedence over the environment variable when both are specified.

  • When missing, the default is to reject all web requests resolving to a non-global IP.
  • When set to a comma-separated list of CIDR-formatted networks (e.g. 192.168.0.0/16,10.0.0.0), then web requests to the networks from the list will be permitted. Web requests to the non-global IPs not part of the list will still be rejected.
  • When set to any, all web requests will be permitted regardless of the target IP, similar to the behavior of Meilisearch v1.34.0 and lower. Use this option when you control both the machine and the configuration of the deployed Meilisearch instance.

Acknowledgments

Thanks to Gabriel Rodrigues (aka Texugo), for reporting this vulnerability and for helping us improve the security of Meilisearch.

v1.34.0

Compare Source

🌈 Improvements

Easy search over your network of machines

useNetwork field in POST /indexes/{:indexUid}/search

The search query object passed in the body of POST /indexes/{:indexUid}/search now accepts an optional boolean useNetwork. When present and set to true, the search is executed "as-if" it was a remote federated search over all remotes in the network.

That is, the following:

Search request 
// POST /indexes/movies/search
{
  "q": "Batman dark knight returns 1",
  "filter": "genres IN [Action, Adventure]",
  "facets": ["genres"],
  "useNetwork": true, // ✨ NEW
  "limit": 5
}

Is executed by Meilisearch as if it was the following, assuming a network of 3 Meilisearch instances with names "0", "1" and "2":

Equivalent multi-search request 
// POST /multi-search
{
    "federation": {
        "limit": 5,
        "facetsByIndex": {
            "movies": [
                "genres"
            ]
        },
        "merge": {}
    },
    "queries": [
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "0"
            },
            "q": "Batman dark knight returns 1",
            "filter": "genres IN [Action, Adventure]"
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "1"
            },
            "q": "Batman dark knight returns 1",
            "filter": "genres IN [Action, Adventure]"
        },
        {
            "indexUid": "movies",
            "federationOptions": {
                "remote": "2"
            },
            "q": "Batman dark knight returns 1",
            "filter": "genres IN [Action, Adventure]"
        }
    ]
}

Resulting in:

Search Response 
{
  "hits": [
    {
      "id": 123025,
      "title": "Batman: The Dark Knight Returns, Part 1",
      "overview": "Batman has not been seen for ten years. A new breed of criminal ravages Gotham City, forcing 55-year-old Bruce Wayne back into the cape and cowl. But, does he still have what it takes to fight crime in a new era?",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/kkjTbwV1Xnj8wBL52PjOcXzTbnb.jpg",
      "release_date": 1345507200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.9894586894586894,
        "remote": "2"
      }
    },
    {
      "id": 142061,
      "title": "Batman: The Dark Knight Returns, Part 2",
      "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city.  Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg",
      "release_date": 1357171200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9894558963186414,
        "remote": "1"
      }
    },
    {
      "id": 16234,
      "title": "Batman Beyond: Return of the Joker",
      "overview": "The Joker is back with a vengeance, and Gotham's newest Dark Knight needs answers as he stands alone to face Gotham's most infamous Clown Prince of Crime.",
      "genres": [
        "Animation",
        "Family",
        "Action",
        "Science Fiction"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/7RlBs0An83fqAuKfwH5gKMcqgMc.jpg",
      "release_date": 976579200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9427964918160996,
        "remote": "1"
      }
    },
    {
      "id": 155,
      "title": "The Dark Knight",
      "overview": "Batman raises the stakes in his war on crime. With the help of Lt. Jim Gordon and District Attorney Harvey Dent, Batman sets out to dismantle the remaining criminal organizations that plague the streets. The partnership proves to be effective, but they soon find themselves prey to a reign of chaos unleashed by a rising criminal mastermind known to the terrified citizens of Gotham as the Joker.",
      "genres": [
        "Drama",
        "Action",
        "Crime",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/qJ2tW6WMUDux911r6m7haRef0WH.jpg",
      "release_date": 1216166400,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.5784178187403994,
        "remote": "1"
      }
    },
    {
      "id": 49026,
      "title": "The Dark Knight Rises",
      "overview": "Following the death of District Attorney Harvey Dent, Batman assumes responsibility for Dent's crimes to protect the late attorney's reputation and is subsequently hunted by the Gotham City Police Department. Eight years later, Batman encounters the mysterious Selina Kyle and the villainous Bane, a new terrorist leader who overwhelms Gotham's finest. The Dark Knight resurfaces to protect a city that has branded him an enemy.",
      "genres": [
        "Action",
        "Crime",
        "Drama",
        "Thriller"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/vzvKcPQ4o7TjWeGIn0aGC9FeVNu.jpg",
      "release_date": 1342396800,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 2,
        "weightedRankingScore": 0.5772657450076805,
        "remote": "2"
      }
    }
  ],
  "query": "Batman dark knight returns 1",
  "processingTimeMs": 173,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 47,
  "facetDistribution": {
    "genres": {
      "Action": 46,
      "Adventure": 15,
      "Animation": 34,
      "Comedy": 3,
      "Crime": 14,
      "Drama": 6,
      "Family": 15,
      "Fantasy": 8,
      "Horror": 1,
      "Mystery": 4,
      "Romance": 1,
      "Science Fiction": 14,
      "TV Movie": 4,
      "Thriller": 4,
      "Western": 1
    }
  },
  "facetStats": {},
  "requestUid": "019bbcf4-a609-7701-8d82-d370611adfb3",
  "remoteErrors": {}
}

useNetwork requires the network experimental feature to be enabled.

useNetwork query parameter in GET /indexes/{:indexUid}/search

Passing useNetwork=true as a query parameter to GET /indexes/{:indexUid}/search has the same effect as passing useNetwork: true as a field parameter to POST /indexes/{:indexUid}/search

.queries[].useNetwork field in POST /multi-search
  • useNetwork can also be passed as a field of the individual queries inside of a multi-search request.
  • When used on a query in a non-federated search request, it has the same effect as on POST /indexes/{:indexUid}/search for that query
  • When used on a query in a federated search request, the request is executed "as-if" one query per remote of the network had been performed.

Federated search example:

Multi-search request 
{
    "federation": {
        "limit": 5
    },
    "queries": [
        {
            "q": "Batman returns",
            "indexUid": "mieli",
            "useNetwork": true
        },
        {
            "q": "Superman returns",
            "indexUid": "mieli",
            "useNetwork": true
        }
    ]
}
Multi-search response 
{
  "hits": [
    {
      "id": 364,
      "title": "Batman Returns",
      "overview": "While Batman deals with a deformed man calling himself the Penguin, an employee of a corrupt businessman transforms into the Catwoman.",
      "genres": [
        "Action",
        "Fantasy"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/jKBjeXM7iBBV9UkUcOXx3m7FSHY.jpg",
      "release_date": 708912000,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 0,
        "weightedRankingScore": 1.0,
        "remote": "1"
      }
    },
    {
      "id": 1452,
      "title": "Superman Returns",
      "overview": "Superman returns to discover his 5-year absence has allowed Lex Luthor to walk free, and that those he was closest to felt abandoned and have moved on. Luthor plots his ultimate revenge that could see millions killed and change the face of the planet forever, as well as ridding himself of the Man of Steel.",
      "genres": [
        "Science Fiction",
        "Action",
        "Adventure"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/qIegbn6DSUYmggfwxOBNOVS35q.jpg",
      "release_date": 1151452800,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 1.0,
        "remote": "0"
      }
    },
    {
      "id": 324249,
      "title": "Requiem for Krypton: Making 'Superman Returns'",
      "overview": "A detailed behind-the-scenes documentary on the making of Superman Returns.",
      "genres": [
        "Documentary"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/eC1XKswKSoyDyJXXZszLTuwUHli.jpg",
      "release_date": 1164672000,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.9907407407407408,
        "remote": "1"
      }
    },
    {
      "id": 294294,
      "title": "Saltwater",
      "overview": "This American Indie drama follows several endearing characters as they wade through life seeking happiness, peace and ultimately, love. Will (Ronnie Kerr, Vampire Boys 2, Shut Up and Kiss Me) leaves the Navy after many years, soon reunites old friends and begins to start his new civilian life. His friend Rich (Bruce L Hart) tries to set him up with ruggedly handsome Josh (Ian Roberts-a former Australian professional rugby player, actor and model-Cedar Boys, Superman Returns, Little Fish). While there is immense chemistry between the two, timing and certain ideals never seem to align. When a shocking tragedy happens the two are paired up to pick up the pieces and sort through the after effects. Saltwater is a story about men of all ages, finding love, losing friends, navigating their way through life and knowing it's the journey rather then the destination that's important.",
      "genres": [
        "Romance",
        "Drama"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/bDnLdYqpH9abHo4ASMPKiInx8dm.jpg",
      "release_date": 1342310400,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 1,
        "weightedRankingScore": 0.966931216931217,
        "remote": "1"
      }
    },
    {
      "id": 142061,
      "title": "Batman: The Dark Knight Returns, Part 2",
      "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city.  Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.",
      "genres": [
        "Action",
        "Animation",
        "Mystery"
      ],
      "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg",
      "release_date": 1357171200,
      "_federation": {
        "indexUid": "mieli",
        "queriesPosition": 0,
        "weightedRankingScore": 0.8697089947089947,
        "remote": "1"
      }
    }
  ],
  "processingTimeMs": 247,
  "limit": 5,
  "offset": 0,
  "estimatedTotalHits": 97,
  "requestUid": "019bbd3a-5106-70e0-94fc-f58b2f0c28c8",
  "remoteErrors": {}
}
Limitations
  • Facet search referencing useNetwork are not supported
  • The chat route cannot use useNetwork at the moment: doing so is not trivial implementation-wise, because chat route expects to be able to open the index (to fetch chat configs), but federated search only opens the indexes once during a short critical section.

By @​dureuill in #​6101

Federated search supports page and hitsPerPage

Pass federation.page and federation.hitsPerPage with the same meaning as in a regular search request to use exhaustive pagination in the federated search

By @​dureuill in #​6101

Speed up settings changes when removing searchable

The settings indexer is more efficient when users are removing searchable attributes from the searchable fields.

By @​VedantMadane in #​6109

🔒 Security

Solves a low-severity timing attack vulnerability on key comparison by using constant-time comparison

By @​curquiza in #​6077

🔩 Maintenance

Remove some unwanted dependencies

New Contributors

❤️ Thanks again @​VedantMadane for the contribution to this release!

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.33.1...v1.34.0

v1.33.1: 🐞

Compare Source

In Meilisearch v1.33.1, we released a security fix that affected the dump import, improvements to vector store relevance in massive databases, and a fix related to ranking scores.

🔐 Security Fix
  • Cloud users: you don't need to do anything. We found no evidence of exploitation of this vulnerability on Meilisearch Cloud.
  • Open-source users: if you allow importing dumps from an untrusted source, we recommend you update to v1.33.1

All versions of Meilisearch before v1.33.0 are vulnerable to a path traversal vulnerability involving the dump import functionality.

Importing a specially crafted dump could result in giving access to the Meilisearch instance to arbitrary, specifically formatted files, present on the file system of the Meilisearch instance.

✨ Enhancements
  • We updated the vector store to trigger linear scanning even on bigger databases, leading to improved performance and so better result quality when the search cutoff is reached. This applies in particular when the number of filtered candidates is small relative to the number of documents in the index by @​Kerollmops in #​6113.
🐛 Bug Fixes
  • We fixed a bug where only the first non-blocking buckets were taken for the non-final ranking rules. This improves the quality of search results when the search cutoff triggers, especially when vector search and a sort are involved by @​Kerollmops in #​6113.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.33.0...v1.33.1

v1.33.0: 🐞

Compare Source

✨ Enhancement

  • Add /fields route to get all the fields of an index by @​YoEight in #​6082
    Adds a new POST /indexes/{indexUid}/fields endpoint that returns detailed metadata about all fields in an index. This endpoint provides comprehensive information about each field's configuration, including display, search, filtering, and localization settings.

  • Implement parallel cleanup of old field IDs by @​Kerollmops in #​6100
    We reduce the time required to perform the dumpless upgrade for instances before v1.32.0 by multi-threading database fetches. By doing that, we noticed improvements from 2 hours and 50 minutes to a bit less than 7 minutes.

  • Bump hannoy to 0.1.4-nested-rtxns by @​Kerollmops in #​6103
    We updated our internal vector store to speed up the dumpless upgrade by improving the graph rebuilding and improving the speed and relevance of the search by using the explore factor as a limit to stop document searches rather than the query limit.

🪲 Bug fixes
🔒 Security
🔩 Miscellaneous

Thank you @​Vipul-045 for your first contribution ❤️

v1.32.2: 🐟

Compare Source

🐛 Bug fixes

  • Do not panic when doing a dumpless upgrade on empty indexes with configured embeddings by @​Kerollmops in #​6102

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.32.1...v1.32.2

v1.32.1: 🐟

Compare Source

🌈 Improvements

Skip cleaning up the field-ID-based databases

Introduce a MEILI_EXPERIMENTAL_DISABLE_FID_BASED_DATABASES_CLEANUP env var to opt out of the field ID-based database cleanup when upgrading a Meilisearch from versions inferior to 1.32.0.

by @​ManyTheFish in #​6096

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.32.0...v1.32.1

v1.32.0: 🐟

Compare Source

🌈 Improvements

Log Search performance trace

Introduces comprehensive progress tracking and logging for search operations in Meilisearch. It adds detailed timing information for each step of the search process, enabling better observability and performance analysis.

by @​ManyTheFish in #​6072

Extract document operations from payloads in parallel

We accelerate document indexing by processing a large number of tasks in batches or a large number of records in parallel. We expedited the preparation of the payloads by extracting the various changes and assigning internal IDs in parallel. We achieved a 7x speedup on a four-million-document insertion using four CPUs, and the performance scales with the number of CPUs.

The indexedDocuments field in tasks using skipCreation no longer precisely reflects the number of document operations performed, specifically for POST and PUT operations. This count may be higher than the actual number of operations, but it doesn't affect the computation; only the reported count is impacted. We prioritize speed over perfect accuracy here, and the documents are still correctly indexed as before.

by @​Kerollmops in #​6080

🐛 Bug fixes

Vector sort: Bucket documents with same similarity

Fixed vector sort bucketing so documents with identical similarity scores are grouped together, ensuring subsequent ranking rules are applied correctly.

by @​dureuill in #​6081

Properly Delete Documents from FID-Based Databases

Fixes a bug where changing searchableAttributes from ["*"] to a subset of fields left orphaned data in fid-based databases, causing corruption and warnings during search.

by @​ManyTheFish in #​6076

Rebuild the graph links when dumpless-upgrading

Bumps hannoy to v0.1.3-nested-rtxns, which fixes graph-related recall issues and adds a method to rebuild graph links to recover previously malformed graphs. Also fixes a minor issue in the dumpless upgrade flow where the upgrade description was not displayed correctly and related operations were not properly associated with the upgrade.

by @​Kerollmops in #​6055

🛠️ Maintenance and Misc.

Update JS SDKs tests to use pnpm instead of yarn

Updated the JavaScript SDK tests to use pnpm instead of yarn in CI workflows, switching the package manager across test configurations to ensure the SDK test suite runs correctly and consistently with the current tooling.

by @​Strift in #​6075

Adapt JS tests in SDK tests CI

Updated the SDK tests CI workflow for the JavaScript SDKs

by @​curquiza in #​6050

Bump lru from 0.16.2 to 0.16.3

Fix Stacked Borrows violation in IterMut.

by @​dependabot[bot] in #​6087

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.31.0...v1.32.0

v1.31.0: 🦃

Compare Source

🌈 Improvements

🗄️ [Enterprise Edition] Make the S3-streaming snapshots an Enterprise Edition feature

The recently introduced S3-streaming snapshots feature is now available as an Enterprise Edition feature. From now on, you'll need a license to use this feature when using Meilisearch as a self-hosted solution. Note that this version introduces a breaking change regarding the S3-streaming snapshot feature, which is no longer available in the Community Edition; however, on-disk snapshots remain accessible. You can read our BUSL license for contact information, if you like. Note that if you are using the Community Edition of Meilisearch between version 1.25 and this release, you can freely use the S3 Streaming feature without an Enterprise Edition license.

by @​Kerollmops in #​6057

🔏 [Enterprise Edition] Support AWS IRSA to authenticate to S3 for snapshotting

We just introduced support for IRSA authentication to do snapshots on AWS. IRSA allows the use of short-lived access and secret keys to upload snapshots through S3. This feature is available under the Enterprise Edition and can be accessed through two experimental CLI parameters.

by @​paulden in #​6044

✍️ Allow strict document update without creating missing documents

Adds an optional skipCreation boolean query parameter to POST and PUT on /indexes/{index}/documents. When set to true, documents that don't exist in the index are silently ignored rather than created. Default is false, preserving existing behavior.

by @​YoEight in #​6053

🐛 Bug fixes

🛠️ Maintenance and Misc.

v1.30.1: 🐸

Compare Source

What's Changed

🐛 Bug Fixes

Fix task attribution during index swap to prevent cross-index task loss by @​YoEight in #​6059

This change fixes the parenting of the tasks when doing an index swap.

Hotfix: log a warning when FieldidsWeightsMap is missing entry by @​ManyTheFish in #​6064

This hotfix avoids the encounter of following error during a search request:

{
  "message": "Inside `<query>`: Index `<index_uid>`: internal: missing <field_id> in the fieldids weights mapping.",
  "code": "internal",
  "type": "internal",
  "link": "https://docs.meilisearch.com/errors#internal"
}

🫂 New Contributors

v1.30.0: 🐸

Compare Source

🌈 Improvements

Up and down network scaling

Since v1.19.0, Meilisearch Enterprise Edition allows the automatic sharding of documents over multiple Meilisearch instances, enabling scaling to more documents than a single instance would accommodate.

Meilisearch v1.30.0 adds the ability to modify the number of participants in sharding, without having to start over sending documents to a new cluster containing the number of desired machines.

To make this possible, Meilisearch v1.30.0 introduces breaking changes. These breaking changes only affect the users of the experimental network feature who enabled automatic sharding (network.sharding = true). Users of the stable features are not affected.

Usage
Setting up the initial network
  1. Pick a leader machine that will receive all tasks. Calling a route that creates a dcument, settings or network-related task on a machine that is not the leader will now return an error.
  2. Send your network topology to the leader by calling PATCH /network:
// PATCH /network
{
  "self": "ms0",
  "leader": "ms0", // must be equal to `self`
  "remotes": {
    "ms0": {
      "url": "URL_OF_MS0",
      "searchApiKey": "SEARCH_API_KEY_OF_MS0",
      "writeApiKey": "WRITE_API_KEY_OF_MS0",
    },
    "ms1": {
      "url": "URL_OF_MS1",
      "searchApiKey": "SEARCH_API_KEY_OF_MS1",
      "writeApiKey": "WRITE_API_KEY_OF_MS1",
    }
  }
}
  1. The network is automatically propagated to other members of the network.
  2. Send settings and documents as usual, but exclusively to the leader. They will be propagated to all participants in the network, and each participant will process a piece of the documents.
Upgrading from v1.29 or earlier
  1. We recommend using the experimental dumpless upgrade feature to go from Meilisearch v1.13+ to Meilisearch v1.29.
  2. When using the experimental dumpless upgrade and the Meilisearch instance already has a network instance with sharding set to true, then the network object will be modified so that the leader is the first remote in alphabetic order. For instance, if you network contains remotes: A, B, C, the leader will be set to A.
Adding a new remote
  1. Call PATCH /network on the leader with the information about the new remote:
{
  "remotes": {
  // add information about the new remote
  "ms2": {
      "url": "URL_OF_MS2",
      "searchApiKey": "SEARCH_API_KEY_OF_MS2",
      "writeApiKey": "WRITE_API_KEY_OF_MS2",
    }
  // information about existing remotes does not need to be repeated
}
  1. The new network will be propagated from the leader to all remotes (including the new remote ms2).
  2. All remotes will register a new networkTopologyChange task that will "rebalance" the documents between the existing remotes and the new remote, that is, ms0 and ms1 will send parts of their documents to ms2
Removing a remote
  1. Call PATCH /network on the leader by setting any removed remote to null:
{
  "remotes": {
  // set removed remote to null
  "ms2": null
  // information about existing remotes does not need to be repeated
}
  1. The new network will be propagated from the leader to all remotes (including to the old remote ms2 that will then no longer participate in the network).
  2. All remotes will register a new networkTopologyChange task that will "rebalance" the documents between the remaining remotes, that is, ms2 will send its documents between ms0 and ms1
List of changes
List of changes, some of which are breaking
  1. Breaking change: The Network object returned or edited by the /network route is modified in the following way:
    • the sharding boolean is removed
    • a leader field is added as an optional string. When it is not null, it has the same effect (and more) than having sharding: true in the previous iteration of the Network object. The leader is used as a check when receiving task creation requests.
    • a version field is added as a UUID, defaulting to the null UUID. The version is used when processing tasks.
  2. Breaking change: When a network.leader is set, calling one of the following routes will fail with not_a_leader error if the target's network.self is not the same as its network.leader:
    • POST /indexes
    • PATCH/DELETE /indexes/{:indexUid}
    • POST/PUT/DELETE /indexes/{:indexUid}/documents
    • POST /indexes/{:indexUid}/documents/delete
    • POST /indexes/{:indexUid}/documents/delete-batch
    • POST /indexes/{:indexUid}/documents/edit
    • PATCH/DELETE /indexes/{:indexUid}/settings and settings sub-routes
    • PATCH /network if the target is the new leader
    • POST /swap-indexes
  3. Breaking change: when a leader is set, PATCH /network no longer returns a Network object. Rather, it spawns a new NetworkTopologyChange task, and returns the summarized task view.
  4. Breaking change: Tasks are duplicated by the leader to the entire network when calling the following routes:
    • POST /indexes (new to this PR)
    • PATCH/DELETE /indexes/{:indexUid} (new to this PR)
    • POST/PUT/DELETE /indexes/{:indexUid}/documents (was already the case before this PR)
    • POST /indexes/{:indexUid}/documents/delete (was already the case before this PR)
    • POST /indexes/{:indexUid}/documents/delete-batch (was already the case before this PR)
    • POST /indexes/{:indexUid}/documents/edit (was already the case before this PR)
    • PATCH/DELETE /indexes/{:indexUid}/settings and settings sub-routes (new to this PR)
    • PATCH /network if the target is the new leader (new to this PR)
    • POST /swap-indexes (new to this PR)
  5. New NetworkTopologyChange tasks that perform the following:
    1. Execute any remaining task to process with a network.version lower than the network task's version
    2. Iterate over all documents in all indexes, determine their new shard, and send the document to the remote that must now have it in the new version , deleting it from the local DB
      • The export route code has been factored and specialized to allow this
      • Should the export to a remote fail, the corresponding documents are kept locally
      • If there are no documents to send for an index, still call the documents addition with an empty payload and appropriate headers containing the expected metadata
      • If there are no documents to send for an entire remote, call the network route with specific headers containing the expected metadata
    3. Wait for and process tasks from the remotes of the previous version of the network.
  6. Breaking change: When importing dumps, we drop the self and leader from the network
  7. Network topology change tasks can be cancelled. In this case the state will be the current one (any moved documents will stay that way). Cancellation needs to happen on all machines.

by @​dureuill in #​6000

🛠️ Maintenance

Asset availability note

🌈 The Meilisearch binary is available again for meilisearch-enterprise-macos-amd64 and meilisearch-macos-amd64. It was not available for Meilisearch v1.29.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.29.0...v1.30.0

v1.29.0: 🐑

Compare Source

Build compatibility note

The git binary must now be present at build time to populate the commitSha1 field of the /version field.

This change was made for build performance reasons.

by @​dureuill in #​6030

🌈 Improvements

Another piece of the settings indexer is available: searchable and exact attributes

The new settings indexer scales better, supports near-instant cancellations and displays the progress of the indexing operation.

Previously, the new settings indexer was enabled only if the only changes in a settings batch were to embedder settings. In Meilisearch v1.29.0, the new settings indexer will be enabled if the change is any combination of:

  • searchableAttributes
  • exactAttributes
  • proximityPrecision
  • embedders (as before)

Any other change to settings appearing in a batch will cause the batch to use the legacy settings indexer.
Additionally, the new settings indexer is currently disabled by default for Cloud users.

OSS users who would like to disable the new settings indexer should pass the MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS environment variable to true.

by @​Kerollmops in #​5983

Enable the new vector store by default for new indexes

Meilisearch v1.21.0 introduced a new vector store backend providing better performance and relevancy.

Starting with v1.29.0, any newly created index will default to the new backend.
Existing indexes will be left unchanged.

It is still possible to explicitly choose the vector store backend, please refer to the relevant experimental feature discussion page.

by @​Kerollmops in #​6004

Support more models for huggingFace embedder

You can now select models with the XLM Roberta architecture when generating embeddings locally on CPU or GPU with the huggingFace embedder.

by @​qdequele in #​6018

🦋 Bug fixes

🔧 Maintenance and Misc.

Last week was a Quality of Life week, and while we still had improvements in the pipe, the bulk of our work was dedicated to maintenance tasks.

Most notably, the CI is now faster, going from over one hour to less than 30 minutes, and also more reliable as it automatically tests the dumpless upgrade.

  • New workload to run declarative tests. This is, in particular, very useful to automatically test the dumpless upgrade. By @​Mubelotix in #​5861
  • The code that applies the dumpless upgrade migrations was rewritten to make it easier to maintain. By @​dureuill in #​6029
  • We no longer run macOS and Windows tests at PR time. These CI jobs were very slow and given their limited impact they will only be run on the nightly builds. Ny @​Kerollmops in #​6021
  • Send notifications for Kubernetes integration when releasing by @​curquiza in #​6023
  • Introduce xtask sub-command to generate prototype tag names with the expected nomenclature by @​Kerollmops in #​6022
  • Fix misc. CI issues by @​dureuill in #​6026

Asset availability note

⚠️ The Meilisearch binary is not available for meilisearch-enterprise-macos-amd64 and meilisearch-macos-amd64 due to a compilation oversight. #​6037 aims at fixing this for future releases.

The more recent meilisearch-enterprise-macos-apple-silicon and meilisearch-macos-apple-silicon are fine.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.28.2...v1.29.0

v1.28.2: 🐩

Compare Source

This release fixes a bug affecting the Prometheus metrics route in versions 1.28.0 and 1.28.1, specifically when the instance has too many tasks. The issue is visible as high memory usage and could cause the instance to be OOM-killed. If you are using the /metrics route, we recommend deleting all succeeded or failed tasks in the index using the dedicated route or upgrading to at least v1.28.2.

🐛 Bug fixes

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.28.1...v1.28.2

v1.28.1: 🐩

Compare Source

This release features two fixes: one to ensure that we correctly upload the Linux-amd64 binaries for the Community and Enterprise editions, and one contributed by an external developer to ensure that we still return documents that don't contain the sortable attribute after those that do.

🐛 Bug Fixes
🫂 New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.28.0...v1.28.1

v1.28.0: 🐩

Compare Source

This release introduces improvements to language support and separates the community and enterprise binary editions. We now offer binaries under the BUSL-1.1 license, identified by the "enterprise" term in their names, in addition to our MIT-licensed binaries, which retain their original names. Docker images for the enterprise edition are available in the getmeili/meilisearch-enterprise repository.

📝 Licensing
  • Separation of EE and CE. CE remains the default binary, and the name does not change by Louis on #​6011
✨ Enhancement
  • Charabia v0.9.9: introduce a better word segmentation for Thai, Khmer, and German languages by @​ManyTheFish in #​6007
  • Expose batch progress traces on the metrics route to improve the indexing debugging experience by @​Kerollmops in #​5956
🔩 Miscellaneous
🫂 New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.27.0...v1.28.0

v1.27.0: 🦮

Compare Source

This release improves the batch size for better performance. It also fixes bugs with the embedders that could skip some documents during generation and resolves an issue with the document route that displayed the same documents on multiple pages. It improves the quality of error messages when uploading snapshots to S3, which helps with debugging.

⚙️ Compatibility support
  • Update macOS platform version in the CI by @​Kerollmops in #​6001
    Meilisearch MacOS binaries now generated with MacOS Sonoma (macos-14)
✨ Enhancement
🪲 Bug fixes
  • Fix issue that could cause Meilisearch to skip some documents when performing embedding operations by @​dureuill in #​5995
    • Every available_parallelismth document in a batch was ignored for the purpose of embedding when using a Hugging Face embedder #​5976
    • Every 40th document in a batch was ignored for the purpose of embedding when using a REST embedder with only one embedding per request
    • To verify if documents in your database have been affected:
      1. enable the multimodal exp. feature
      2. search or fetch with filter: NOT _vectors EXISTS to find documents without vectors.
  • Fix /documents/fetch bug that could cause duplicated search results when paginating sorted documents by @​ManyTheFish in #​5999

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.26.0...v1.27.0

v1.26.0: 🐛

Compare Source

✨ Enhancements

Allow to attach custom metadata in the document addition or update tasks

  • To make it easier to keep track of which documents were processed by Meilisearch, it is now possible to attach an arbitrary string to all routes that create document-related tasks.
  • Tasks created with this custom metadata will display the passed metadata when accessed by the tasks route or sent in webhooks.
  • To use this feature, add the customMetadata query parameter to any supported route:
POST /indexes/{indexUid}/documents?customMetadata=my-metadata-for-the-task
  • Note that, as usual for query parameters, the value of the parameter must be URL-encoded.
  • List of supported routes:
POST /indexes/{indexUid}/documents
PUT /indexes/{indexUid}/documents
DELETE /indexes/{indexUid}/documents/{documentId}
POST /indexes/{indexUid}/documents/delete-batch
POST /indexes/{indexUid}/documents/delete
POST /indexes/{indexUid}/documents/edit
DELETE /indexes/{indexUid}/documents
  • Sample output of GET /tasks for tasks with metadata:
{
  "results": [
    {
      "uid": 37,
      "batchUid": 37,
      "indexUid": "mieli",
      "status": "succeeded",
      "type": "documentDeletion",
      "canceledBy": null,
      "details": {
        "deletedDocuments": 31944
      },
      "error": null,
      "duration": "PT0.511099S",
      "enqueuedAt": "2025-11-06T16:33:37.816237Z",
      "startedAt": "2025-11-06T16:33:37.821591Z",
      "finishedAt": "2025-11-06T16:33:38.33269Z",
      "customMetadata": "removeall"
    },
    {
      "uid": 36,
      "batchUid": 36,
      "indexUid": "movies",
      "status": "succeeded",
      "type": "documentAdditionOrUpdate",
      "canceledBy": null,
      "details": {
        "receivedDocuments": 31968,
        "indexedDocuments": 31944
      },
      "error": null,
      "duration": "PT3.192271S",
      "enqueuedAt": "2025-10-30T10:31:12.896073Z",
      "startedAt": "2025-10-30T10:31:12.911905Z",
      "finishedAt": "2025-10-30T10:31:16.104176Z",
      "customMetadata": "foo"
    }
  ],
  "total": 38,
  "limit": 2,
  "from": 36,
  "next": 35
}

by @​dureuill in #​5963

Support more models for huggingFace embedder

You can now select models with the modernBERT architecture when generating embeddings locally on CPU or GPU with the huggingFace embedder.

This unlocks for instance Ruri v3 and other models

by @​hayatosc in #​5980

🧪 Experimental: embedder failure modes

You can now decide to ignore some embedder-related errors. Either:

  1. Errors related to a document template not rendering properly
  2. Errors related to an embedding request to an embedder failing (this includes missing vectors in userProvided embedders)
  3. Or both kinds of errors.

When errors are ignored, the corresponding documents will not have embeddings, but the associated batch of tasks will not be marked as failed.

Of course, ignoring errors means that it is harder to notice an issue with embedders, so use this feature parsimoniously.

To enable the feature:

  • Customers of the Cloud, please ask the support.
  • OSS users, please use the MEILI_EXPERIMENTAL_CONFIG_EMBEDDER_FAILURE_MODES and set it to a comma-separated list of errors to ignore, with the possible values:
    1. ignore_document_template_failures to ignore document template failures
    2. ignore_embedder_failures to ignore embedder failures
    • For example: ignore_document_template_failures,ignore_embedder_failures ignores both kinds of failures

by @​dureuill in #​5984

🧪 Experimental: timeout control for REST embedders

You can now control the duration before a REST embedder request times out.

  • Customers of the Cloud, please ask the support.
  • OSS users, please use the MEILI_EXPERIMENTAL_REST_EMBEDDER_TIMEOUT_SECONDS, which must be a positive integer.

by @​dureuill in #​5984

🔩 Misc

👥 Contributors

Many thanks to our new contributors @​hayatosc and @​xuhongxu96 ❤️

v1.25.0: 🐈‍⬛

Compare Source

✨ Enhancement

🔬 [Experimental]: Search personalization by @​ManyTheFish in #​5775

Add the ability to dynamically rerank the search results based on Cohere using a personalized prompt.
For more information on how to set it up, see the dedicated experimental feature discussion.

🔬 [Experimental]: Upload snapshot tarballs to S3 by @​Kerollmops in #​5948

Add the ability to upload snapshots directly to S3. It has many advantages, such as being able to stream the entire process and effectively utilizing multipart technology to send chunks of data in parallel.
For more information on how to use it, see the dedicated experimental feature discussion.

🪲 Bug fixes

⚠️ [Breaking - Security] Redact Authorization header in webhooks by @​dureuill in #​5968

The value of the Authorization header is now redacted when getting webhook, getting webhooks, or in the object returned when posting a new webhook or deleting a webhook.

  • Impact on Cloud: Similarly to embedder API, the UI should make sure to never send the Authorization header back after it has been redacted
  • Technically a breaking change, as users could previously get the key value back when getting the webhook, and that will no longer be possible
🚰 Fix the LMDB fork memory leak by @​Kerollmops in #​5967

This bug was causing crashes in the recent indexer optimizations. If you deactivated these optimizations by setting the following environment variables:

MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_PREFIX_POST_PROCESSING=true
MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_FACET_POST_PROCESSING=true

You can now safely reactivate them without experiencing memory leaks.

🇩🇪 Hotfix German word segmentation by @​ManyTheFish in meilisearch/charabia#360

German word segmentation relies on a word dictionary to segment words, but if a word is not part of the dictionary, it is cut into bigrams. The segmenter will now skip segmenting unknown words:

Source: "Feuchteschutz"
Before: ["Fe" "uc" "ht" "es, "ch", "utz"]
After:  ["Feuchteschutz"]

Source: "insgesamt"
Before: ["in" "sg" "es" "amt"]
After:  ["insgesamt"]

If you have a Meilisearch database containing German words, you must reindex your data manually.

🇨🇳 Prevent splitting of numbers and English words in Chinese text segmentation by @​JinheLin in meilisearch/charabia#354

It’s very common for Chinese, numbers, and English to appear together in the same sentence.
We now ensure that numbers and English are not segmented differently between segmenters:

Source: "我从2025年开始学习Rust语言。"
Before: ["我", "从", "2", "0", "2", "5", "年", "开始", "学习", "R", "u", "s", "t", "语言", "。"]
After:  ["我", "从", "2025", "年", "开始", "学习", "Rust", "语言", "。"]

If you have a Meilisearch database containing Chinese words, you must reindex your data manually.

🔩 Miscellaneous

Thanks to @​JinheLin, @​dureuill, @​Kerollmops, and @​ManyTheFish for their contribution! 🎉

v1.24.0: 🦞

Compare Source

This release features some improvements with the interaction of the vector store and the searchCutoffMs when using the "vectorStore": "experimental" index setting. It also introduces the metadata header Meili-Include-Metadata on the search request that adds a metadata field to the response. These metadatas contains one uid by query and a reminder of the indexUid and its primary key. We also introduced minor bug fixes around the compaction to improve the interaction with task cancellation.

✨ Enhancement
🔩 Miscellaneous
👥 New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.23.0...v1.24.0

v1.23.0: 🐘

Compare Source

This release introduces a new compact route on the index routes, which appends a new compaction task to the queue. Meilisearch uses an LMDB environment by index, and indexes start to fragment after some time. We have noticed that the indexes generally have 30% fragmentation. By defragmenting the environment, we've seen large (2-4x) speed-ups in terms of search and indexation. This is primarily due to the reordering of the LMDB internal pages and the removal of scattered free pages throughout the file, thereby relocating the content to the beginning.

We also worked on parallelizing the post-processing of facets. We noticed that a lot of time was spent iterating over the prefixes of the index in a single-threaded loop. We redesigned this part of the indexation to make it multi-threaded. We have seen a 4x and 6x improvement in terms of time spent on this operation.

✨ Improvements

🦋 Bug Fixes

🔩 Miscellenaous

New Contributors

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.22.1...v1.23.0

v1.22.3: 🐦‍🔥

Compare Source

This version contains a minor fix that affects remote federated search users. If you are not a remote federated search user, it is not necessary to migrate from v1.22.x.

🦋 Bugfixes

  • v1.22.2 raised the remote federated search timeout for waiting nodes from 5 to 30s. This version makes it configurable by setting the environment variable MEILI_EXPERIMENTAL_REMOTE_SEARCH_TIMEOUT_SECONDS to a positive integer value. Please note that no CLI flag or configuration entry is available. By @​dureuill in #​5932

v1.22.2: 🐦‍🔥

Compare Source

🦋 Bugfixes

  • Remote federated search would declare remotes as "timeout'd" after 5s. This timeout was raised to 30s to accomodate some search configurations. By @​dureuill in #​5919

v1.22.1

Compare Source

🐛 Bug Fixes

❤️ Huge thanks to our contributors: @​dureuill and @​irevoire.

v1.22.0: 🐦‍🔥

Compare Source

🚀 Enhancements

  • Introduce a new geo backend to store geojson and filter on polygon
    1. Make the _geojson field filterable
    2. Then send your documents with a _geojson field filled with a valid geojson
    3. Filter your documents with the new _geoPolygon filter, or the old _geoBoudingBox and _geoPoints filter

🐛 Bug Fixes

❤️ Huge thanks to our contributors: @​nnethercott, @​Kerollmops, @​ManyTheFish, @​dureuill and @​irevoire.

Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.21.0...v1.22.0

v1.21.0: 🐷

Compare Source

🚀 Enhancements

  • Introduce a new vector store backend for better performance, especially if using the binary quantization
    1. Enable the new vectorStoreSetting experimental feature
    2. Then change the vectorSetting index setting to "experimental" for the indexes where you want to try the new vector store
  • Add Persian support (update charabia to v0.9.7) (#​5848) @​ManyTheFish

🐛 Bug Fixes

  • Observing the progress trace during indexing no longer removes parts of the trace (#​5884) @​irevoire
  • Fix dumpless upgrade decoding error when upgrading with a rest embedder (#​5886) @​dureuill.
    • In case you had encountered the issue, use the dumpless upgrade to v1.21 to fix it.

❤️ Huge thanks to our contributors: @​ja7ad, @​agourlay, @​Kerollmops, @​ManyTheFish, @​dureuill and @​irevoire.

v1.20.0: 🦟

Compare Source

🚀 Enhancements

🐛 Bug Fixes

🔒 Security

⚙️ Maintenance/misc

❤️ Huge thanks to our contributors: @​ManyTheFish, @​arithmeticmean, @​curquiza, @​dureuill, @​irevoire, @​shreeup and dependabot[bot].

v1.19.1: 🪸

Compare Source

🐛 Performance improvements

Enhance hybrid search with filter performances

In previous versions of Meilisearch, mixing hybrid search with filters, as shown below, could multiply the search time by hundreds.

{
  "q": "hello world",
  "limit": 100,
  "filter": "tag=science"
  "hybrid": {
    "semanticRatio": 0.5,
    "embedder": "default"
  }
}

Meilisearch will now directly compute the semantic distance with the filtered candidates if only a few candidates come from the filter, instead of searching for the closest embeddings matching the filter in the vector database.

v1.19.0: 🪸

Compare Source

🚀 Enhancements

Automatically shard documents to scale horizontally

Meilisearch can now automatically distribute documents between multiple instances using the new sharding feature.

Find a guide on implementing sharding in the documentation.

[!NOTE]
Sharding is an advanced feature available exclusively in Meilisearch Enterprise Edition (EE).

The EE features are governed by the Business Source License 1.1, which allows you to use, test, and develop with sharding for free in non-production environments. Please reach out to us before using it in production.

Added in #​5784 by @​dureuill

🐛 Bug Fixes

  • Takes the allowed max memory of the container when computing the max memory to use (#​5729) @​martin-g

❤️ Huge thanks to our contributors: @​Kerollmops, @​dureuill and @​martin-g.

v1.18.0: 🕷️

Compare Source

🚀 Enhancements

❤️ Huge thanks to our contributors: @​Kerollmops, @​Mubelotix, @​irevoire and @​qdequele.

v1.17.1: 🐀

Compare Source

🚀 Enhancements

⚙️ Maintenance/misc

v1.17.0: 🐀

Compare Source

[!NOTE]
Want to make your search feel more natural? Try our new chat completions route and turn your queries into conversations. Easy to set up, works with your favorite LLMs.

Enhancements
Bugs
  • Turn chat settings to PATCH by @​Mubelotix in #​5807
    ⚠️ This fix leads to a breaking change on: PUT → PATCH. Integrations and SDKs will adapt to this change.
  • Fix snapshotCreation task being included in snapshot by @​Mubelotix in #​5773
Maintenance

v1.16.0: 🦚

Compare Source

Meilisearch v1.16 introduces two main features: multimodal embeddings and a new /export route. Multimodal embeddings use AI-powered search to index images in addition to textual documents. The /export route simplifies migrating from a local Meilisearch instance to Meilisearch Cloud.

🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment happens between 4 to 48 hours after a new version becomes available.

Some SDKs might not include all new features. Consult the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️).

New features and updates 🔥

Experimental feature: Multimodal embeddings

v1.16 allows indexing and searching non-textual documents, as well as performing searches with image queries. This new feature uses multimodal embedders to provide a common semantic representation for images, texts, and any other piece of data.

Usage

First, enable the multimodal experimental feature:

curl \
  -X PATCH 'MEILISEARCH_URL/experimental-features/' \
  -H 'Content-Type: application/json'  \
  --data-binary '{
    "multimodal": true
  }'

Next, pick an embedder provider that supports multimodal embeddings such as Cohere or VoyageAI to start building the embedding configuration.

The following is an example configuration for multimodal embedder using VoyageAI:

curl \
  -X PATCH 'MEILISEARCH_URL/indexes/INDEX_NAME/settings/embedders' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "voyage": {
      "source": "rest",
      "url": "https://api.voyageai.com/v1/multimodalembeddings",
      "apiKey": "VOYAGE_API_KEY",
      "indexingFragments": {
        "text": {
          "value": {
            "content": [
              {
                "type": "text",
                "text": "A movie titled {{doc.title}} whose description starts with {{doc.overview|truncateWords:20}}."
              }
            ]
          }
        },
        "poster": {
          "value": {
            "content": [
              {
                "type": "image_url",
                "image_url": "{{doc.poster}}"
              }
            ]
          }
        }
      },
      "searchFragments": {
        "poster": {
          "value": {
            "content": [
              {
                "type": "image_url",
                "image_url": "{{media.poster}}"
              }
            ]
          }
        },
        "image": {
          "value": {
            "content": [
              {
                "type": "image_base64",
                "image_base64": "data:{{media.image.mime}};base64,{{media.image.data}}"
              }
            ]
          }
        },
        "text": {
          "value": {
            "content": [
              {
                "type": "text",
                "text": "{{q}}"
              }
            ]
          }
        }
      },
      "request": {
        "inputs": [
          "{{fragment}}",
          "{{..}}"
        ],
        "model": "voyage-multimodal-3"
      },
      "response": {
        "data": [
          {
            "embedding": "{{embedding}}"
          },
          "{{..}}"
        ]
      }
    }}

The configuration above sets up Meilisearch to generate vectors for two fields: text and poster. It also allows users to perform searches with an image URL, a raw image, or regular text.

Use the new media search parameter together with one of the searchFragments you specified in your embedder to search with an image:

curl -X POST 'MEILISEARCH_URL/indexes/INDEX_NAME/search' \
  -H 'content-type: application/json' \
  --data-binary '{
    "media": {
      "poster": "https://image.tmdb.org/t/p/w500/pgqj7QoBPWFLLKtLEpPmFYFRMgB.jpg"
    },
    "hybrid": {
      "embedder": "EMBEDDER_NAME"
    }
  }'

You can also perform a text search with q and hybrid:

curl -X POST 'MEILISEARCH_URL/indexes/INDEX_NAME/search' \
  -H 'content-type: application/json' \
  --data-binary '{
    "q": "A movie with lightsabers in space",
    "hybrid": {
      "embedder": "voyage",
      "semanticRatio": 0.5
    }
  }'

Meilisearch performs searches all fields with embeddings when parsing hybrid queries targeting indexes with multimodal embedders.

For more information about this feature, please refer to its public usage page

Done by @​dureuill in #​5596

The new /export route

v1.16 introduces a new /export route that allows transferring documents between instances without having to create a dump or a snapshot. This feature is particularly useful when migrating from a local machine to Meilisearch Cloud.

Usage

To transfer data between instances, query /export and point its url parameter to the URL of the target instance:

curl \
  -X POST 'MEILISEARCH_URL/export' \
  -H 'Content-Type: application/json' \
  --data-binary '{
    "url": "http://localhost:7711"
  }'

This will generate an export and task start migrating data between instances. Depending on the target instance, you may also have to supply an API key with full admin permissions in the apiKey parameter. Consult the documentation for an exhaustive list of accepted parameters.

If the request fails, Meilisearch will retry a few times before setting its status to failed. You may also cancel an export task manually. In this case, Meilisearch will interrupt the task locally, but not in the target instance.

Done by @​kerollmops with the help of @​mubelotix in #​5670

Other improvements

Fixes 🐞

Misc

❤️ Thanks again to our external contributors:

v1.15.2: 🦘

Compare Source

This patch release introduces a major fix and some minor fixes.

Major fix: searchable attributes database bug

Some searchable fields were removed from the searchable databases when they were removed from the filterableAttributes setting.
This made them unsearchable, although they were still precise in the searchableAttributes setting.

Fixed by @​ManyTheFish in #​5660

Minor fixes

v1.15.1: 🦘

Compare Source

Meilisearch v1.15.1 adds new experimental conversational features and enables LLM-driven chat features.

🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment takes 4 to 48 hours after a new version becomes available.

Some SDKs might not include all new features. Please look over the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️).

Chat with your indexes

After enabling the experimental chat feature, you can create a chat workspace with the appropriate settings.
We have a guide on how to set up a good chat interface for your indexes.

curl -X POST 'http://localhost:7700/chats/my-assistant/settings' \
  -H 'Content-Type: application/json' \
  -d '{
    "source": "openAi",
    "apiKey": "sk-abc..."
  }'

Then by using the official OpenAI SDK you'll be able to chat with your indexes.

import OpenAI from 'openai';

const client = new OpenAI({
  baseURL: 'http://localhost:7700/chats/my-assistant',
  apiKey: 'YOUR_MEILISEARCH_CHAT_API_KEY',
});

const completion = await client.chat.completions.create({
  model: 'gpt-3.5-turbo',
  messages: [{ role: 'user', content: 'What is Meilisearch?' }],
  stream: true,
});

for await (const chunk of completion) {
  console.log(chunk.choices[0]?.delta?.content || '');
}

Done by @​Kerollmops in #​5556.

v1.15.0: 🦘

Compare Source

Meilisearch v1.15 adds a new typo tolerance setting, allowing you to disable typo tolerance for numbers. It also enables comparison operators for string filters.

🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment takes 4 to 48 hours after a new version becomes available.

Some SDKs might not include all new features. Please look over the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️).

New features and updates 🔥

Disable typo tolerance for numbers

Set typoTolerance.disableOnNumbers to true to disable typo tolerance for numbers:

curl -X POST 'http://localhost:7700/indexes/movies/settings' \
  -H 'Content-Type: application/json' \
  -d '{
    "typoTolerance": {"disableOnNumbers": true}
  }'

Deactivating the typo tolerance on numbers can be helpful when trying to reduce false positives, such as a query term 2024 returning results that include 2025 and 2004. It may also improve indexing performance.

Done by @​ManyTheFish in #​5494.

Lexicographic string filters

This release allows you to filter strings lexicographically by enabling comparison operators (<, <=, >, >=, TO) on string values:

curl -X POST 'http://localhost:7700/indexes/movies/search' \
  -H 'Content-Type: application/json' \
  -d '{
    "filter": "release_date >= '2024-06'"
  }'

This new feature can be particularly useful when filtering human-readable dates.

Done by @​dureuill in #​5535.

Other improvements

Fixes 🐞

  • Fix _matchesPosition length calculation to improve client-side cropping by @​shaokeyibb in #​5446
  • Fix _geo ranking rule by @​HDT3213 in #​5487
  • Fix a panic in the search that could happen when looking for typos with a search prefix having more than 65k possible hits in the DB by @​dureuill in #​5564
  • Make sure that passing MEILI_EXPERIMENTAL_MAX_NUMBER_OF_BATCHED_TASKS to 0 results in Meilisearch never processing any kind of task. By @​irevoire in #​5565
  • Forbid value 0 for maxTotalHits in the index settings by @​irevoire in #​5566
  • No longer reject documentTemplates that use array filters on documents (e.g. join) by @​dureuill in #​5593

Misc

❤️ Thanks again to our external contributors:

v1.14.0: 🦫

Compare Source

Meilisearch v1.14 gives more granular control over which parts of filters you can disable for indexing performance optimization. This release also includes composite embedders, which can improve embedding generation during search and indexing, and a new route to retrieve multiple documents by their IDs.

🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment happens between 4 to 48 hours after a new version becomes available.

Some SDKs might not include all new features. Consult the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️).

New features and updates 🔥

Granular filterable attribute settings

v1.14 gives you more control over which types of filter you want to disable in your searches. This allows you to further optimize indexing speeds by letting you activate only the filter features you need.

Use PATCH /indexes/INDEX_NAME/settings to specify which filters you want to enable for each attribute in your documents:

{
	"filterableAttributes": [
	  {
	    "attributePatterns": ["genre", "artist"],
	    "features": {
	      "facetSearch": true,
	      "filter": {
	        "equality": true,
	        "comparison": false
	      }
	    }
	  },
	  {
	    "attributePatterns": ["rank"],
	    "features": {
	      "facetSearch": false,
	      "filter": {
	        "equality": true,
	        "comparison": true
	      }
	    }
	  }
	]
}

For more details about this feature, please refer to the dedicated documentation page.

Done by @​ManyTheFish in #​5254.

Composite embedders

This feature allows using different embedders at search and indexing time. This can be useful when optimizing AI-powered search performance. For example, you may prefer to use:

  • A remote embedder during indexing, as remote embedders have higher bandwidth and can generate more embeddings per second
  • A local embedder when answering to search queries, as local embedders have lower latency and can respond more quickly to user input

To use the feature, follow these steps:

  1. Enable the Composite embedders feature with the Meilisearch Cloud interface, or with the /experimental-features route:
curl MEILISEARCH_URL/experimental-features \
  -H 'Content-Type: application/json'  \
  -d '{"compositeEmbedders": true}'
  1. Next, create an embedder, setting its source to "composite" and defining one searchEmbedder and one indexingEmbedder:
{
  "embedders": {
    "text": {
      "source": "composite",
      "searchEmbedder": {
        "source": "huggingFace",
        "model": "baai/bge-base-en-v1.5",
        "revision": "a5beb1e3e68b9ab74eb54cfd186867f64f240e1a"
      },
      "indexingEmbedder": {
        "source": "rest",
        "url": "https://URL.endpoints.huggingface.cloud",
        "apiKey": "hf_XXXXXXX",
        "documentTemplate": "Your {{doc.template}}",
        "request": {
          "inputs": [
            "{{text}}",
            "{{..}}"
          ]
        },
        "response": [
          "{{embedding}}",
          "{{..}}"
        ]
      }
    }
  }
}
  1. Once the composite embedder has been created, Meilisearch will use its indexingEmbedder during indexing and searchEmbedder when responding to user queries

For more details about this feature, please refer to its public usage page.

Done by @​dureuill in #​5371 and #​5401.

Retrieve multiple documents by ID

It is now possible to retrieve multiple documents by their IDs:

curl -H 'Content-Type: application/json' MEILISEARCH_URL/indexes/INDEX_UID/documents -d '{ "ids": ["cody", "finn", "brandy", "gambit"] }'

{
  "results": [
    {
      "id": "brandy",
      "info": 13765493
    },
    {
      "id": "finn",
      "info": 35863
    },
    {
      "id": "cody",
      "info": 122263
    },
    {
      "id": "gambit",
      "info": 22222
    }
  ],
  "offset": 0,
  "limit": 20,
  "total": 4
}

[!WARNING]
Documents are not returned in the queried order. Non-existent documents are ignored.

Done by @​dureuill in #​5384.

Other improvements

Fixes

Misc

⚠️ Please consider that the batches stats content can change anytime.

❤️ Thanks again to our external contributors:

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on the first day of the month"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [getmeili/meilisearch](https://github.com/meilisearch/meilisearch) | minor | `v1.13.3` → `v1.55.0` | --- > ⚠️ **Warning** > > Some dependencies could not be looked up. Check the [Dependency Dashboard](issues/3) for more information. --- ### Release Notes <details> <summary>meilisearch/meilisearch (getmeili/meilisearch)</summary> ### [`v1.55.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.55.0): 🔭 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.54.3...v1.55.0) ### 🌈 Improvements #### Preview the effect of a dynamic search rule Apply an inline-specified dynamic search rule to a search query. Search query objects in the following endpoints now have an additional, optional `inlineRule` parameter. When present and not `null`, then Meilisearch will check if query satisfies the conditions of the dynamic search rule specified in `inlineRule`, and if so will apply the actions of the rule as if it had been sent to the `PATCH /dynamicSearchRule/{:uid}` endpoint. Additionally, if the `Meili-Include-Metadata` header is present in the request with the value `true`, then the `metadata` in the response will contain information about whether the conditions of the inline rule were satisfied and if not why. Meilisearch Cloud will use this backend feature to implement a preview UI for dynamic search rules. Using `inlineRule` requires Meilisearch Enterprise Edition and the `dynamicSearchRules` experimental feature. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6669](https://github.com/meilisearch/meilisearch/pull/6669) ##### Details 1. There is a new `InlineRule` object with the following field: 1. `uid`, string, mandatory: unique ID of the rule. If there is already a rule with this id, then the inline rule will replace the existing rule for the duration of this search query. 2. `active`, boolean, optional, defaults to `true`: whether the rule is active. The actions of an inactive inline rule never apply to the search, but its conditions are still checked 3. `conditions`: `RuleConditions` object, identical to the `conditions` field in the body of `PATCH /dynamic-search-rules/{:uid}` 4. `actions`: `RuleActions` object, identical to the `actions` field in the body of `PATCH /dynamic-search-rules/{:uid}` 5. `precedence`: integer, optional, identical to the `precedence` field in the body of `PATCH /dynamic-search-rules/{:uid}` 2. The `POST /indexes/{:indexUid}/search` body has an additional, optional (defaults to `null`) `inlineRule` field which is an `InlineRule` object. 3. In the `POST /multi-search` body, the objects inside the `queries` array have an additional, optional (defaults to `null`) `inlineRule` field which is an `InlineRule` object. ##### Examples <details> <summary>Passing a search rule specific to the user making the request</summary> ```jsonc // POST /indexes/movies/search { "q": "super hero", "inlineRule": { "uid": "user-likes-batman", "actions": { "scale": [ { // filter recent Batman movies "filter": "hero = batman AND release_time = fresh", "weight": 1.2 // moderate relevancy boost } ] } } } ``` </details> <details> <summary>Previewing the effect of a search rule</summary> ```jsonc // POST /multi-search -H 'Meili-Include-Metadata: true` { "queries": [ // base query without inline rule { "q": "fashion", "filter": "color = blue AND category = shirt" }, // same query with inline rule { "q": "fashion", "filter": "color = blue AND category = shirt", "inlineRule": { "uid": "special-sales", "conditions": { "query": { "words": "pants", }, "filter": { "values": { "color": "yellow", "stock_intent": "destock" } } } } } ] } ``` Response: ```jsonc { // [ ... ] some other fields "results": [ // results without the rule { "hits": [ ... ] // documents returned without the rule }, // results with the rule { // [...] some other fields "hits": [...], // documents returned with the rule. Here the same, because the conditions of the rules are not satisfied "metadata": { // [...] some other fields "inlineRuleConditionOutcomes": { "satisfiesActiveCondition": true, "satisfiesQueryWordsCondition": { "missingWord": "pants" }, "satifiesFilterCondition": { "missingConstraintOnField": { "field": "stock_intent" }, "unmetConstraintOnField": "field": "color" } } } } ] } ``` </details> #### Improve `showPerformanceDetails` at search time When setting `showPerformanceDetails` to `true` in a search request, the response's `performanceDetails` will now display an entry for the facet distribution computation. <details><summary>New trace entries</summary> **Request** ```bash curl -X POST 'http://localhost:7700/indexes/movies/search' \ -H 'Content-Type: application/json' \ -d '{ "q": "batman", "facets": ["genres"], "showPerformanceDetails": true, "limit": 3 }' ``` **Response** ```json { "hits": [ # ... ], "query": "batman", "processingTimeMs": 4, "limit": 3, "offset": 0, "estimatedTotalHits": 68, "facetDistribution": { "genres": { #... } }, "facetStats": {}, "requestUid": "01a12f80-0e1b-7632-b4f3-c8d4914048c9", "performanceDetails": { "wait in queue": "68.58µs", "preprocess filters > prepare": "100.25µs", "preprocess filters": "100.42µs", "process > prepare": "115.54µs", "process > send to remote": "102.71µs", "process > execute local > load field ids map": "30.88µs", "process > execute local > query[0] > tokenize query": "265.38µs", "process > execute local > query[0] > evaluate query": "890.96µs", "process > execute local > query[0] > keyword ranking": "425.04µs", "process > execute local > query[0]": "2.95ms", "process > execute local > pin hits": "9.92µs", "process > execute local > format": "94.62µs", "process > execute local > facet distribution > compute facet distribution": "315.75µs", "process > execute local > facet distribution > compute facet stats": "27.71µs", "process > execute local > facet distribution": "432.62µs", "process > execute local": "3.81ms", "process > wait for remote": "50.96µs", "process > merge": "905.62µs", "process": "5.07ms" } } ``` Three additional steps: ```json "process > execute local > facet distribution > compute facet distribution": "315.75µs", "process > execute local > facet distribution > compute facet stats": "27.71µs", "process > execute local > facet distribution": "432.62µs", ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6644](https://github.com/meilisearch/meilisearch/pull/6644) ### 🦋 Fixes #### Avoid panic at search time during formatting Documents containing raw unicode codepoints (e.g. `\u03b1`) would cause a panic at search time when formatting results for highlighting when using some segmenters. A failure at the segmenter's level no longer causes a panic. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6673](https://github.com/meilisearch/meilisearch/pull/6673) #### Fix search performance of ranking score threshold > \[!IMPORTANT]\ > This fix modifies the relevancy of the engine in some circumstances. This is allowed as per our back-compatiblity policy. To avoid a performance sink when using the `rankingScoreThreshold` parameter in a search, Meilisearch now guarantees that **the search will stop after evaluating the first document whose score is below the threshold**. Previously Meilisearch would try to evaluate more documents, which could lead to evaluating all documents in the database, causing a very long search time. By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6661](https://github.com/meilisearch/meilisearch/pull/6661) #### Prevent unsupported `binaryQuantization` deactivation in embedder settings > \[!WARNING]\ > This fix introduces a breaking change in the Meilisearch API. Because the previous behavior would corrupt the embeddings in the database, this is allowed by our back-compatibility policy. Since the exact value of embeddings is not retained when the embedder is configured for binary quantize embeddings, disabling the binary quantization on an index is not allowed. Unfortunately, an oversight in the API allowed to accidentally disable binary quantization by passing `binaryQuantization: null` in a setting update. This now results in an error. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6656](https://github.com/meilisearch/meilisearch/pull/6656) ### 🔩 Miscellaneous - Maintainability: replace some `unreachable!()` code paths with static typing by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6670](https://github.com/meilisearch/meilisearch/pull/6670) - Add GHA to enforce benchmarks label on each PR by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6663](https://github.com/meilisearch/meilisearch/pull/6663) - Add link to MCP guide in generated API reference by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6650](https://github.com/meilisearch/meilisearch/pull/6650) - Add link to agentic search demo & fix links by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6655](https://github.com/meilisearch/meilisearch/pull/6655) - Small changes to CONTRIBUTING.md by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6668](https://github.com/meilisearch/meilisearch/pull/6668) - Bump actions/setup-java from 5.7.0 to 6.0.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6662](https://github.com/meilisearch/meilisearch/pull/6662) - Fix OpenAPI docs by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6667](https://github.com/meilisearch/meilisearch/pull/6667) - CI: Fix flaky tests by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6674](https://github.com/meilisearch/meilisearch/pull/6674) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.54.3...v1.55.0> ### [`v1.54.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.54.3) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.54.2...v1.54.3) This release contains an important stability fix for Meilisearch. Update from v1.54.2 is recommended. See [#&#8203;6658](https://github.com/meilisearch/meilisearch/pull/6658) for details ### [`v1.54.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.54.2) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.54.1...v1.54.2) Meilisearch v1.54.2 contains an important fix for users of the `dynamicSearchRule` experimental feature. ### 🦋 Fixes - Trying to process, display, delete or cancel dynamic search rules update tasks that were created in Meilisearch v1.53 or prior no longer causes internal errors. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6651](https://github.com/meilisearch/meilisearch/pull/6651). Thanks to [@&#8203;connorabbas](https://github.com/connorabbas) for their report in [#&#8203;6646](https://github.com/meilisearch/meilisearch/issues/6646) ❤️ ### [`v1.54.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.54.1) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.54.0...v1.54.1) ##### 🪲 Bug fixes - Make the embedder setting change succeed when the embedder's API key is expired by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6640](https://github.com/meilisearch/meilisearch/pull/6640) - Ignore geo errors when updating or deleting existing docs by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6638](https://github.com/meilisearch/meilisearch/pull/6638) ##### 🔩 Miscellaneous - Aggregate the analytics from the MCP route by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6639](https://github.com/meilisearch/meilisearch/pull/6639) ### [`v1.54.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.54.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.53.3...v1.54.0) ### 💥 Breaking Changes Meilisearch v1.54.0 makes breaking changes to the `dynamicSearchRules` experimental features. - For Cloud users, rules will be migrated automatically, and the UI will adapt to the new API. Only the first change on rulelist might affect users that directly get rules through the API. - If upgrading with `--upgrade-db`, rules will be migrated automatically. 1. The `POST /dynamic-search-rules` endpoint now returns `actions` as an object with 2 fields instead of a list: 2. `pin` is an array of `Pin` objects with the following fields: 1. `id`, String, mandatory: document id of the document to pin 2. `position`: positive or zero number, mandatory: position where to pin the document 3. `indexUid`, optional, defaults to `null`, uid of the index that this action applies to. If `null` or missing, the action applies to any index containing a document with the provided `id`. 3. `scale` is an array of `Scale` objects with the following fields: 1. `weight`, positive or zero number, mandatory: scaling factor to multiply with the selected documents' innate relevancy score 2. `ids`, array of strings, optional: list of document ids whose document's relevancy score should be scaled by the provided weight 3. `filter`: Meilisearch filter without a foreign filter, optional: a filter on the index that is resolved to determine a list of selected documents 4. `indexUid`, optional, defaults to `null`, uid of the index that this action applies to. If `null` or missing, the action applies to any index. 4. The `PATCH /dynamic-search-rules/{:ruleUid}` endpoint now expects a rule with the modified `actions` field. See changes to `POST /dynamic-search-rules` for details. 5. The uid `__meilisearch_metadata` is now reserved and cannot be used as a `ruleUid` in `PATCH /dynamic-search-rules/{:ruleUid}` ### 🌈 Enhancements #### Boost, demote and hide documents with search rules - A dynamic search rule can now boost, deboost or hide documents by defining a new "scale" action that selects some documents by filter and/or an explicit list of ids and exposes a scale factor as a `weight`: - If the weight is > 1.0, then the selected documents are boosted - If the weight is < 1.0, then the selected documents are deboosted (demoted) - If the weight is = 0.0, then the selected documents are hidden and don't appear in search results (unless if they are also pinned) - ⚠️ Because the factor is applied to the relevancy rules, it has little measurable effect when the first ranking rule is not a relevancy rule. - Score details for a pinned document now contains an additional `ruleUid` field indicating the name of the rule that resulted in the document being pinned. ⚠️ As a result, end-users can find out the uid of applied rules by looking at ranking score details. Please keep any sensitive information in the description of the rule instead ⚠️ - Score details for a scaled document now contains an additional `scale` field, with order `0`. The scale field is an object with the following fields: - `order`: order of application of the rule. Always 0 - `actions`: an array of `ScaleAction`s, where each `ScaleAction` contains the following fields: - `ruleUid`: the name of the rule that was applied - `weight` the weight of the rule that was applied - `totalWeight`: the total multiplicative factor computed as the product of the individual `.actions[].weight`. - New environment variables controlling how much scale operations can occur: - `MEILI_EXPERIMENTAL_DSR_FUEL_MAX_SCALE_ACTIONS`: maximum number of applicable (at least one selected document) scale actions in a single search. Range 1-255, default 10 - `MEILI_EXPERIMENTAL_DSR_FUEL_SCALE_FUEL`: maximum number of combinations of scale constraint that are evaluated in a single search. Range 1-255, default 10. ##### Examples <details><summary>Boosting "Batman" product for a festival</summary> 1. Creating the search rule ```jsonc // PATCH /dynamic-search-rule/batman-festival { "conditions": { "time": { "start": "2026-09-21T19:00:00Z", "end": "2026-09-28T18:59:00Z" }, }, "actions": { "scale": [ { "filter": "series = batman", "weight": 4.0 } ] } } ``` 2. Once the DSR update task has been processed and the festival begins on September 21st, make a search query: ```jsonc { "q": "superhero returns prequel", "showRankingScoreDetails": true } ``` 3. Observe the ranking of documents ```jsonc "hits": [ { "id": "batman-returns", "title": "Batman Returns", "series": "batman", "_rankingScore": 0.30808080808080807, "_rankingScoreDetails": { "scale": { "order": 0, "actions": [ { "ruleUid": "batman-festival", "weight": 4.0 } ], "totalWeight": 4.0 }, "words": { "order": 1, "matchingWords": 1, "maxMatchingWords": 3, "score": 0.3333333333333333 }, "typo": { "order": 2, "typoCount": 0, "maxTypoCount": 1, "score": 1.0 }, "proximity": { "order": 3, "score": 1.0 }, "attributeRank": { "order": 4, "score": 1.0 }, "wordPosition": { "order": 5, "score": 0.9090909090909092 }, "exactness": { "order": 6, "matchType": "noExactMatch", "matchingWords": 1, "maxMatchingWords": 1, "score": 0.3333333333333333 } } }, { "id": "superman-returns", "series": "superman", "title": "Superman Returns - The Prequels", "_rankingScore": 0.9628456221198156, "_rankingScoreDetails": { "words": { "order": 0, "matchingWords": 3, "maxMatchingWords": 3, "score": 1.0 }, "typo": { "order": 1, "typoCount": 0, "maxTypoCount": 3, "score": 1.0 }, "proximity": { "order": 2, "score": 0.5714285714285714 }, "attributeRank": { "order": 3, "score": 1.0 }, "wordPosition": { "order": 4, "score": 0.9032258064516128 }, "exactness": { "order": 5, "matchType": "noExactMatch", "matchingWords": 2, "maxMatchingWords": 3, "score": 0.25 } } }, // ... ], "processingTimeMs": "[duration]", "limit": 20, "offset": 0, "estimatedTotalHits": 42, "requestUid": "[uuid]" } ``` </details> <details> <summary>Demoting out-of-stock products</summary> ```jsonc // PATCH /dynamic-search-rules/out-of-stock { "actions": { "scale": [ { "filter": "availability = \"out of stock\"", "weight": 0.5 } ] } } ``` </details> <details> <summary>Hiding discontinued products</summary> ```jsonc // PATCH /dynamic-search-rules/discontinued { "actions": { "scale": [ { "filter": "availability = discontinued", "weight": 0.0 } ] } } ``` </details> By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6549](https://github.com/meilisearch/meilisearch/pull/6549) #### MCP endpoint We introduce a new MCP protocol on the /mcp path. It implements [the HTTP+SSE Transport version of the protocol](https://modelcontextprotocol.io/specification/2024-11-05/basic/transports#http-with-sse). You can register the Meilisearch MCP in your favorite LLM, e.g., Claude Code, Codex. Note that the MCP route is using bearer authentication and doesn't support OAuth authentication. Enable the `mcpRoute` experimental feature to use the feature. by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6629](https://github.com/meilisearch/meilisearch/pull/6629) #### Improve search performance details in multi-search The performance details in a federated search now separate the timing per query <details> <summary>Example</summary> ```json "performanceDetails": { "wait in queue": "1.36ms", "preprocess filters > prepare": "985.00µs", "preprocess filters > send to remote": "220.00µs", "preprocess filters > execute local > evaluate filter": "139.00µs", "preprocess filters > execute local": "1.61ms", "preprocess filters > wait for remote": "35.97ms", "preprocess filters": "39.01ms", "process > prepare": "96.00µs", "process > send to remote": "118.00µs", "process > execute local > load field ids map": "63.00µs", "process > execute local > query[0] > evaluate filter": "84.00µs", "process > execute local > query[0] > tokenize query": "163.00µs", "process > execute local > query[0] > evaluate query": "116.00µs", "process > execute local > query[0] > keyword ranking": "634.00µs", "process > execute local > query[0]": "1.52ms", "process > execute local > pin hits": "29.00µs", "process > execute local > format": "36.00µs", "process > execute local": "2.90ms", "process > wait for remote": "37.24ms", "process > merge": "82.00µs", "process": "40.45ms", "hydrate > send to remote": "38.00µs", "hydrate > execute local": "35.00µs", "hydrate > wait for remote": "41.00µs", "hydrate": "295.00µs", "merge facets": "51.00µs" } ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6631](https://github.com/meilisearch/meilisearch/pull/6631) ### 🔩 Miscellaneous - Remove `HashMap` transmute in indexer by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6622](https://github.com/meilisearch/meilisearch/pull/6622) - Bump `lru` to 0.18.4 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6633](https://github.com/meilisearch/meilisearch/pull/6633) - Simplify Rust install and update Rust to v1.98.1 by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6601](https://github.com/meilisearch/meilisearch/pull/6601) - Bump most dependencies by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6589](https://github.com/meilisearch/meilisearch/pull/6589) - Bump `actions/setup-go` from 6.5.0 to 7.0.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6611](https://github.com/meilisearch/meilisearch/pull/6611) - Fix grammar and broken Markdown links in error code descriptions by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6626](https://github.com/meilisearch/meilisearch/pull/6626) - Fix typo by [@&#8203;simpleqt](https://github.com/simpleqt) in [#&#8203;6619](https://github.com/meilisearch/meilisearch/pull/6619) #### New Contributors - [@&#8203;simpleqt](https://github.com/simpleqt) made their first contribution in [#&#8203;6619](https://github.com/meilisearch/meilisearch/pull/6619) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.53.2...v1.54.0> ### [`v1.53.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.53.3) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.53.2...v1.53.3) This release contains an important stability fix for Meilisearch. Update from v1.53.2 is recommended. See [#&#8203;6658](https://github.com/meilisearch/meilisearch/pull/6658) for details ### [`v1.53.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.53.2): 🖇️​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.53.1...v1.53.2) #### 🪲 Bug fixes - Remove 100ms penalty on task replication by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6612](https://github.com/meilisearch/meilisearch/pull/6612) - Do not highlight stop-words by [@&#8203;harismuzaffer](https://github.com/harismuzaffer) in [#&#8203;6595](https://github.com/meilisearch/meilisearch/pull/6595) - Include last indexed documents in exactness ranking rule when updating searchable attributes in settings by [@&#8203;harismuzaffer](https://github.com/harismuzaffer) in [#&#8203;6604](https://github.com/meilisearch/meilisearch/pull/6604) #### 🔒 Security - Tie authorization to index opening by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6610](https://github.com/meilisearch/meilisearch/pull/6610) #### **🔩 Miscellaneous** - Add context for CorruptedTaskQueue error in message by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6615](https://github.com/meilisearch/meilisearch/pull/6615) - Allow generating a description for the error codes by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6609](https://github.com/meilisearch/meilisearch/pull/6609) - Update charabia to 0.10.0 by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6602](https://github.com/meilisearch/meilisearch/pull/6602) - Fix typo by [@&#8203;vaibhav8a](https://github.com/vaibhav8a) in [#&#8203;6605](https://github.com/meilisearch/meilisearch/pull/6605) #### New Contributors - [@&#8203;harismuzaffer](https://github.com/harismuzaffer) made their first contribution in [#&#8203;6595](https://github.com/meilisearch/meilisearch/pull/6595) - [@&#8203;vaibhav8a](https://github.com/vaibhav8a) made their first contribution in [#&#8203;6605](https://github.com/meilisearch/meilisearch/pull/6605) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.53.1...v1.53.2> ### [`v1.53.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.53.1): 🖇️​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.53.0...v1.53.1) #### **✨ Enhancement** ##### Add an env var to change the task queue readers > by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6587](https://github.com/meilisearch/meilisearch/pull/6587) Control the maximum number of LMDB read transactions at the same time for the task queue. The following environment variable can be exported to specify the maximum number of simultaneous read transactions: ``` # Only the environment variable can set this parameter MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS=100 ``` Product discussion: <https://github.com/orgs/meilisearch/discussions/806> #### **🔩 Miscellaneous** - Bump mini-dashboard to v0.4.2 by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6585](https://github.com/meilisearch/meilisearch/pull/6585) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.53.0...v1.53.1> ### [`v1.53.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.53.0): 🖇️​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.52.4...v1.53.0) ##### **✨ Enhancement** - Sharding for foreign filters by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6517](https://github.com/meilisearch/meilisearch/pull/6517) - The foreign filter now supports sharding by retrieving the documents through the network when evaluating the foreign filters and hydrating the documents. - The limit of documents that a foreign filter can retrieve has been increased from 100 to 1000. - Adds `indexSize` and `usedIndexSize` returned by `GET /indexes/{index_uid}/stats` and in `GET /stats` by [@&#8203;tpayet](https://github.com/tpayet) in [#&#8203;6563](https://github.com/meilisearch/meilisearch/pull/6563) ##### 🔒 Security - Fix code security issues in GitHub Actions workflows by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6565](https://github.com/meilisearch/meilisearch/pull/6565) - Bump quinn-proto from 0.11.14 to 0.11.16 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6538](https://github.com/meilisearch/meilisearch/pull/6538) ##### **🔩 Miscellaneous** - Bump peter-evans/repository-dispatch from 3.0.0 to 4.0.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6556](https://github.com/meilisearch/meilisearch/pull/6556) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.51.0...v1.53.0> ### [`v1.52.4`](https://github.com/meilisearch/meilisearch/releases/tag/v1.52.4) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.52.3...v1.52.4) This release contains an important stability fix for Meilisearch. Update from v1.52.3 is recommended. See [#&#8203;6658](https://github.com/meilisearch/meilisearch/pull/6658) for details ### [`v1.52.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.52.3): 🐠 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.52.2...v1.52.3) ##### 🪲 Bug fixes - Revert the Speed up the search speed a bit more by [@&#8203;Kerollmops](https://github.com/Kerollmops) introduced in [#&#8203;6542](https://github.com/meilisearch/meilisearch/pull/6542) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.52.2...v1.52.3> ### [`v1.52.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.52.2): 🐠 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.52.1...v1.52.2) ##### 🪲 Bug fixes - Revert the /tasks/stream and /batches/stream SSE routes by [@&#8203;Kerollmops](https://github.com/Kerollmops) introduced in [#&#8203;6533](https://github.com/meilisearch/meilisearch/pull/6533) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.52.1...v1.52.2> ### [`v1.52.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.52.1): 🐠 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.52.0...v1.52.1) ##### 🪲 Bug fixes - Make the health route checks blocking by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6583](https://github.com/meilisearch/meilisearch/pull/6583) - Revert some search progress traces by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6584](https://github.com/meilisearch/meilisearch/pull/6584) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.52.0...v1.52.1> ### [`v1.52.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.52.0): 🐠 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.51.0...v1.52.0) ##### ✨ Enhancement - Introduce the `/tasks/stream` and `/batches/stream` SSE routes by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6533](https://github.com/meilisearch/meilisearch/pull/6533) This **experimental feature** allows establishing a live connection to the engine, avoiding the need to implement long polling and instead letting the engine provide new tasks, batches, and batch progress in a push-based manner. Using this route can drastically reduce network load when retrieving the status of a Meilisearch instance. - Speed up the search a bit more by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6542](https://github.com/meilisearch/meilisearch/pull/6542) We improve the search speed when it comes to formatting the documents by making an `O(n)` operation, where `n` is the number of retrieved documents, become an `O(1)` operation. This improvement can significantly increase search speed when requesting a large (> 20) number of documents. ##### 🪲 Bug fixes - Fix duplicate pins in federated search by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6543](https://github.com/meilisearch/meilisearch/pull/6543) - Skip the settings when nothing changes by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6544](https://github.com/meilisearch/meilisearch/pull/6544) ### [`v1.51.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.51.0): 👽 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.50.0...v1.51.0) ##### ✨ Enhancement - **Add filter condition to DSRs** by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6505](https://github.com/meilisearch/meilisearch/pull/6505) ##### New `filter` rule activation condition ```` Dynamic search rules (DSR) can now declare a new `filter` condition: it contains a single `values` key, whose value is a JSON object. The keys of this `values` JSON object are the facet names (e.g., `color`, `genres`, ...), while their values are the values that a filter must resolve to for these facets, so that the rule is active. <details> <summary>Example of sending a DSR with a filter condition</summary> ```jsonc // PATCH /dynamic-search-rules/test-filter { "conditions": { "filter": { "values": { "color": "red", "category": "shirt" } } }, "actions": [ { "selector": { "id": "red shirt on sales" }, "action": { "type": "pin", "position": 0 } } ] } ``` </details> <details> <summary>Example of search query that enables the DSR above</summary> ```jsonc { "filter": "(category = shirt AND color = red) OR (category = jeans AND color = blue)" } ``` </details> Note that the filter only needs to have one branch resolving to all the facet values declared in the rule for the rule to be active. ```` ##### New `lastUpdatedAt` field ``` Dynamic search rules returned by `GET /dynamic-search-rules/{:ruleUid}` and `POST /dynamic-search-rules` contain an additional `lastUpdatedAt` field. This field is automatically updated with the `enqueuedAt` value of the last task that modified the rule. ``` ##### Rules are listed with the most recently updated first ``` `POST /dynamic-search-rules` now lists rules in descending `lastUpdatedAt` order, meaning that the most recently updated rules will be listed first. ``` ##### New environment variables ``` New environment variables are defined to control the behavior of the DSR fuel: - `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_FUEL` (in range 0..4294967296): controls how many filter constraint combinations Meilisearch will attempt to resolve at search time before giving up and applying partial rules. - `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_OR_FUEL` (in range 0..65536): controls how many filter disjunctions Meilisearch will build when turning a filter to its canonical shape - `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_AND_FUEL` (in range 0..65536): controls how many filter conjunctions Meilisearch will build in total when turning a filter to its canonical shape - `MEILI_EXPERIMENTAL_DSR_FUEL_FILTER_DEPTH_FUEL` (in range 0..256): controls the maximum recursive depth that Meilisearch allows when turning a filter to its canonical shape ``` - **Speed up search requests** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6528](https://github.com/meilisearch/meilisearch/pull/6528) Improves Meilisearch search speed by avoiding unnecessary internal work. We drastically reduced the number of times we retrieve data from disk to a single time across the whole search pipeline. This improvement will have the greatest effect on datasets with a large number of distinct fields across documents. We have seen search speeds up to 5.4x on a dataset with more than 14k different fields. - **Stabilize dumpless upgrade** by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6486](https://github.com/meilisearch/meilisearch/pull/6486) ⚠️ Breaking change following the stabilization of an experimental feature ⚠️ The flag `—-experimental-dumpless-upgrade` is renamed `—-upgrade-db`, keeping the exact same behavior. - **Remove unused experimental features** by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6489](https://github.com/meilisearch/meilisearch/pull/6489) ⚠️ Breaking change: removing the following experimental features ⚠️ - [Replication parameters](https://github.com/orgs/meilisearch/discussions/725): removing `--experimental-replication-parameters` because outdated. We now have another way to handle replication. - [Import dumps with old document indexer fallback](https://github.com/orgs/meilisearch/discussions/851): removing `--experimental-no-edition-2024-for-dumps`. This flag existed to prevent bugs related to our new indexer, which is now stable. - [No snapshot compression](https://github.com/orgs/meilisearch/discussions/833): removing `--experimental-no-snapshot-compaction` because it's not useful anymore. ##### 🪲 Bug fixes - Make sure legacy attribute patterns work by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6531](https://github.com/meilisearch/meilisearch/pull/6531) - Missing support for the shorthand filterable attributes syntax ##### 🔩 Miscellaneous - Add missing logs in multisearch by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6529](https://github.com/meilisearch/meilisearch/pull/6529) - Docs: Fix stale pre-v1.0 supported versions statement by [@&#8203;vishnujayvel](https://github.com/vishnujayvel) in [#&#8203;6524](https://github.com/meilisearch/meilisearch/pull/6524) - Bump sigstore/cosign-installer from 4.1.1 to 4.1.2 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6427](https://github.com/meilisearch/meilisearch/pull/6427) - Bump actions/github-script from 7 to 9 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6425](https://github.com/meilisearch/meilisearch/pull/6425) - Bump actions/upload-artifact from 4 to 7 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6428](https://github.com/meilisearch/meilisearch/pull/6428) #### New Contributors - [@&#8203;vishnujayvel](https://github.com/vishnujayvel) made their first contribution in [#&#8203;6524](https://github.com/meilisearch/meilisearch/pull/6524) ### [`v1.50.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.50.0): 🐐 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.49.0...v1.50.0) Meilisearch v1.50 revamps the [Dynamic Search Rules](https://www.meilisearch.com/docs/capabilities/search_rules/overview), adds support for federated document fetch in sharded configurations, among other improvements #### Breaking changes This release introduces breaking changes for users using some experimental features ##### `dynamicSearchRules` experimental feature ##### Request type changes 1. `priority` has been replaced with `precedence`, which better reflects the behavior (lower precedence means the rule is applied first) 2. `conditions` has been modified from an array to an object with two fields: "query" of type `QueryCondition` and "time" of time `TimeCondition` 3. New type `QueryCondition` that contains the fields `isEmpty` (as previously) and `words` instead of `contains` (same type) 4. It is now possible to pass `isEmpty: false` with `words` in a `QueryCondition`. Passing `isEmpty:true` with `words` still results in a synchronous error. 5. New type `TimeCondition` with fields `start` and `end` (unchanged semantics from previous type). 6. When specifying the `selector` of an `Action`, it is now mandatory to specify an `id`. Previously, it was optional, but the action would never trigger. 7. When listing rules with `POST /dynamic-search-rules`, `filter.attributePatterns` has been replaced with `filter.query`, an optional string that searches in rule `description` and `conditions.query.words`. 8. When calling `DELETE /dynamic-search-rules/{:ruleUid}` or `PATCH /dynamic-search-rules/{:ruleUid}` in a sharded configuration, endpoint will not return a HTTP 400 error if called on a follower remote rather than on the leader. ##### Response changes 1. `PATCH /dynamic-search-rules/{:ruleUid}` and `DELETE /dynamic-search-rules/{:ruleUid}` now register an asynchronous task.. 2. The response is modified to return the registered task instead of the modified dynamic search rule. 3. HTTP 404 is no longer returned if the `{:ruleUid}` portion of the URL refers to a rule that doesn't exist. This is because rules are processed asynchronously, and is consistent with the behavior of `DELETE /indexes/{:indexUid}/documents/{:docId}` for `{:docId}` ##### `network` experimental feature The default behavior for users using the network experimental feature with sharding configured (`leader` not `null`) will change on the following routes: - **GET** `indexes/:uid/documents` - **GET** `indexes/:uid/documents/:document_id` - **POST** `indexes/:uid/documents/fetch` Meilisearch will now fetch the documents from all the shards and not only on the local machine when processing the request. To keep the same behavior as before, users will have to set `useNetwork` to `false` when making their request. #### 🌈 Improvements ##### Scaling up the Dynamic Search Rules - Dynamic search rules scale up to 75K rules without any impact on the search - The API of Dynamic Search Rules has been simplified - It is harder to send conditions that will result in the rules never activating - This also unlocks future improvements such as filter activation conditions for search rules ##### Additions - Add a new `DELETE /dynamic-search-rule` route that deletes all the DSRs - Add the concept of "DSR fuel" that determines how much energy is spent resolving DSR during a search. The fuel is initialized with some default variables that can be overridden using environment variables: - `MEILI_EXPERIMENTAL_DSR_FUEL_MAX_COUNTED_WORDS`: max number of words considered inside of a search query for the purpose of finding `conditions.query.words` constraints. Defaults to 10, max value is 255 - `MEILI_EXPERIMENTAL_DSR_FUEL_MAX_ACTIVE_RULES`: max number of active rules whose actions are evaluated. Defaults to 1000, max value is [`4294967`](https://github.com/meilisearch/meilisearch/commit/4294967295) - `MEILI_EXPERIMENTAL_DSR_FUEL_MAX_PIN_ACTIONS`: max number of pin actions that are applied. Defaults to 100, max value is [`4294967`](https://github.com/meilisearch/meilisearch/commit/4294967295) - `MEILI_EXPERIMENTAL_DSR_FUEL_WORD_FUEL`: max number of constraint combinations that are evaluated for the purpose of finding `conditions.query.words` constraints. Defaults to 4096, max value is [`4294967`](https://github.com/meilisearch/meilisearch/commit/4294967295) By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6484](https://github.com/meilisearch/meilisearch/pull/6484) and [#&#8203;6506](https://github.com/meilisearch/meilisearch/pull/6506) ##### Behavior changes - The `conditions.query.words` behaves differently from `query.contains`: previously, a rule would match if its conditions `query.contains` would be substrings of `q` in the search query in the sense of [`str::contains`](https://doc.rust-lang.org/std/primitive.str.html#method.contains). Now, a rule matches if all the words in `conditions.query.words` appear in `q` (after normalization). For `q = hero super`, `query.contains = super hero` would **not** match, whereas `conditions.query.words = super hero` does now match. This behavior is more in line with regular search, and allows improving performance. - Dynamic search rules are now replicated from the leader to its follower, when in a sharded configuration ##### Federated document fetch routes **GET** `indexes/:uid/documents`, **GET** `indexes/:uid/documents/:document_id` and **POST** `indexes/:uid/documents/fetch` will now fetch the documents from all the shards in the configured network. Moreover, a new `useNetwork` parameter is available to activate or deactivate the usage of the network. By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6495](https://github.com/meilisearch/meilisearch/pull/6495) ##### Support partial wildcards when requesting facets The `facets` parameter in search and federated search now supports more wildcards. Previously, only the single wildcard `"*"` was supported, requesting all filterable fields. Now, patterns *containing* `*` are supported with the same matching rules as in `filterableAttributes.attributePatterns` and `localizedAttributes.attributePatterns`, such as `dogs.*`, which will add to the facet distribution all filterable fields that match the pattern (such as `dogs.intel`, `dogs.kefir`, etc.). By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6497](https://github.com/meilisearch/meilisearch/pull/6497) #### 🦋 Fixes ##### Fix migration from v1.48 and earlier Migration via `--experimental-dumpless-upgrade` would fail in some cases in v1.49, when trying to migrate synonyms that contained no words (empty synonyms, or containing only separator tokens such as `&`). Such synonyms are now ignored during migration, avoiding the issue. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6501](https://github.com/meilisearch/meilisearch/pull/6501) ##### Fix filter memory consumption in some cases In some conditions, the memory consumption of filters would increase quadratically with the length of the filter. This is now resolved for these cases. By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6509](https://github.com/meilisearch/meilisearch/pull/6509) ##### No longer reject some correctly-escaped filters Fix a bug where some filters containing escaped characters (such as \\) would cause search requests to fail with invalid\_search\_filter By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6499](https://github.com/meilisearch/meilisearch/pull/6499) ##### More fault-tolerant S3 snapshots *Potentially* fix an issue when sending a request to AWS S3 to create a new multipart upload, ensuring we resend the request if it fails. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6494](https://github.com/meilisearch/meilisearch/pull/6494) #### 🔩 Miscellaneous changes - Add missing route descriptions for documentation by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6500](https://github.com/meilisearch/meilisearch/pull/6500) - Make the prototype docs clearer by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6503](https://github.com/meilisearch/meilisearch/pull/6503) - Improve maintenability by simplifying partitioning step by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6511](https://github.com/meilisearch/meilisearch/pull/6511) - Fix frequently failing tests on Windows by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6520](https://github.com/meilisearch/meilisearch/pull/6520) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.49.0...v1.50.0> ### [`v1.49.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.49.0): 🪺 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.48.3...v1.49.0) ##### ✨ Enhancement - Improve the synonyms storage by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6466](https://github.com/meilisearch/meilisearch/pull/6466) We improve synonyms' performance by changing how we store and retrieve them during query processing. Users may have experienced performance issues when the number of synonyms in an index was high, resulting in a significant impact on search performance. The Meilisearch support team advised moving the settings and synonyms-as-keywords to the dedicated documents. This is no longer an issue; synonyms are loaded lazily, only when a word matches a synonym. You can see performance improvements of up to 13x, depending on the number of synonyms. ##### 🔩 Miscellaneous - Fix the workflow after broken ranking scores by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6470](https://github.com/meilisearch/meilisearch/pull/6470) - Make OpenAPI rule less strict for routes returning 202 by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6488](https://github.com/meilisearch/meilisearch/pull/6488) ### [`v1.48.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.48.3): v1.48.3 🫎​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.48.2...v1.48.3) ### 🪲 Bug fixes - Fix a rare S3 snapshots bug by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6472](https://github.com/meilisearch/meilisearch/pull/6472) We fixed a rare bug that could appear when using the S3 snapshot system. The bug is a race condition that occurs when we try to recycle internal buffers to reduce memory usage, which can cause an internal error and abort the snapshot upload. - Avoid remote search to return the same document twice by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6473](https://github.com/meilisearch/meilisearch/pull/6473) When using the remote federated search, Meilisearch was returning the same document twice from different machines. This was due to an internal filter that was not forwarded properly to the remote instances. ### **🔩 Miscellaneous** - Add missing searchFilterParam to GET chat workspace settings response by [@&#8203;CaroFG](https://github.com/CaroFG) in [#&#8203;6475](https://github.com/meilisearch/meilisearch/pull/6475) - Split unit tests into separate files (one commit per file) by [@&#8203;0xfandom](https://github.com/0xfandom) in [#&#8203;6468](https://github.com/meilisearch/meilisearch/pull/6468) - Add missing information from pre-openAPI-migration by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6467](https://github.com/meilisearch/meilisearch/pull/6467) #### New Contributors Thanks to [@&#8203;0xfandom](https://github.com/0xfandom), who made his first contribution in [#&#8203;6468](https://github.com/meilisearch/meilisearch/pull/6468) 🎉 **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.48.2...v1.48.3> ### [`v1.48.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.48.2): 🫎 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.48.1...v1.48.2) Meilisearch v1.48.2 and Meilisearch v1.47.1 address CVE-2026-57823 and CVE-2026-57824. We recommend updating if you are in one of the following situations: 1. You have API keys where `indexes` is *not* `["*"]` and where `actions` contains more permissions than: `["search", "documents.*", "indexes.*", "tasks.cancel", "tasks.delete", "tasks.get", "settings.*", "stats.*", "fields.post"]` 2. You have [search tenant tokens](https://www.meilisearch.com/docs/capabilities/security/overview) and either an [embedder](https://www.meilisearch.com/docs/getting_started/glossary#embedder) or a [chat workspace](https://www.meilisearch.com/docs/capabilities/conversational_search/how_to/configure_chat_workspace) - We recommend that users of Meilisearch v1.48 update to Meilisearch v1.48.2 - We recommend that users of Meilisearch v1.47 or lower update to Meilisearch v1.47.1 These versions both fix the following: 1. CVE-2026-57824: Improper authentication leads to privilege escalation: an authenticated user with an index-scoped API and the appropriate set of actions could use global actions to read and write the global state of the Meilisearch instance. Possibly impacted users of Meilisearch Cloud were contacted ahead-of-time. 2. CVE-2026-57823: Improper authentication leads to information disclosure: a user with a search tenant token could get some limited information about the existence of a document outside of the scope of the search rules attached to the tenant token, an indirect information about the content of the document. We detected no trace of exploitation of these vulnerabilities. We thank PuH4ck3rX for reporting these vulnerabilities :heart: ### [`v1.48.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.48.1): 🫎 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.48.0...v1.48.1) Revert [#&#8203;6432](https://github.com/meilisearch/meilisearch/issues/6432) due to a dumpless upgrade bug report. **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.48.0...v1.48.1> ### [`v1.48.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.48.0): 🫎​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.47.1...v1.48.0) ### **✨ Enhancement** #### \[Experimental] Render 🫎​ template route > by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5765](https://github.com/meilisearch/meilisearch/pull/5765) Introduces a new `POST /render-template` route that can be used to render any template or fragment on any input and associated [`renderRoute` experimental feature](https://github.com/orgs/meilisearch/discussions/888) that gates access to the route. This route can be used to test document templates and fragments before and after having configured an embedder. A body payload for the route is of the form: ```jsonc { "template": /* templateTarget object */, "input": /* inputTarget object or null */ } ``` where `template` describes the template or fragment to render, and `input` describes what to use to render the template. Upon calling this route, Meilisearch responds with: ```jsonc { "template": "{{doc.text}}", "rendered": "template text after rendering using the input" } ``` where `template` contains the **un**rendered base text of the document template, or the **un**rendered base JSON object of a fragment, and `rendered` contains the result of rendering the template of the chosen input. If `input` is `null` in the request, then `rendered` is `null` in the response, and the route can be used solely to retrieve a template or fragment from the settings of an index. ##### Before calling the route The API of this route is subject to change, so before calling this route, please enable the `renderRoute` experimental feature: ```sh PATCH /experimental-features --json '{"renderRoute": true}' ``` ##### Examples 1. Rendering a document from an index on a document template from an embedder of that index <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "documentTemplate", "indexUid": "movies", "embedder": "myMoviesEmbedder" }, "input": { "kind": "indexDocument", "indexUid": "movies", "id": "2" } ``` </details> <details><summary>response</summary> ```jsonc { "template": "A movie titled {{doc.title}} whose description starts with {{doc.overview|truncatewords:10}}", "rendered": "A movie titled Ariel whose description starts with Taisto Kasurinen is a Finnish coal miner whose father has..." } ``` </details> 2. Rendering an inline document on a fragment from an embedder of an index <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "indexingFragment", "indexUid": "dogs", "embedder": "multi", "fragment": "captionedImage" }, "input": { "kind": "inlineDocument", "inline": { // pass your document inline as a JSON object "kind": "dog", "name": "iko", "breed": "jack russell", "mime": "image/png", "image": "/9j/4AAQSk..." } } } ``` </details> <details><summary>response</summary> ```jsonc { "template": { "content": [ { "type": "text", "text": "A picture of a {{doc.kind}} of breed {{doc.breed}}" }, { "type": "image_base64", "image_base64": "data:{{doc.mime}};base64,{{doc.image}}" } ] }, "rendered": { "content": [ { "type": "text", "text": "A picture of a dog of breed jack russell" }, { "type": "image_base64", "image_base64": "data:image/png;base64,/9j/4AAQSk..." } ] } } ``` </details> 3. Rendering a search query on a search fragment from a multimodal embedder of an index <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "searchFragment", "indexUid": "testIndex", "embedder": "testEmbedder", "fragment": "justBreed" }, "input": { "kind": "inlineSearch", "inline": { // pass the search query inline "q": "unused", "media": { "name": "iko", "breed": "jack russell" }, "filter": "ignored" } } } ``` </details> <details><summary>response</summary> ```jsonc { "template": "It's a {{ media.breed }}", "rendered": "It's a jack russell" } ``` </details> 4. Rendering an inline document on the document template from the chat settings of an index <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "chatDocumentTemplate", "indexUid": "movies" // no embedder to specify since chat document template is global to index }, "input": { "kind": "indexDocument", "indexUid": "movies", "id": "2" } ``` </details> <details><summary>response</summary> ```jsonc { "template": "{% for field in fields %}{% if field.is_searchable and field.value != nil %}{{ field.name }}: {{ field.value }}\n{% endif %}{% endfor %}", "rendered": "id: 2\ntitle: Ariel\noverview: Taisto Kasurinen is a Finnish coal miner whose father has just committed suicide and who is framed for a crime he did not commit. In jail, he starts to dream about leaving the country and starting a new life. He escapes from prison but things don't go as planned...\ngenres: DramaCrimeComedy\nposter: https://image.tmdb.org/t/p/w500/ojDg0PGvs6R9xYFodRct2kdI6wC.jpg\nrelease_date: 593395200\n" } ``` </details> 5. Rendering a document from an index on an inline document template <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "inlineDocumentTemplate", "inline": "You can pass templates inline as well: nice to test them! {{doc.id}}" }, "input": { "kind": "indexDocument", "indexUid": "movies", "id": "2" } ``` </details> <details><summary>response</summary> ```jsonc { "template": "You can pass templates inline as well: nice to test them! {{doc.id}}", "rendered": "You can pass templates inline as well: nice to test them! 2" } ``` </details> 6. Rendering an inline document on an inline indexing fragment <details><summary>request</summary> ```jsonc // POST /render-template { "template": { "kind": "inlineFragment", "inline": { "json_maps": "supported for fragments", "any_string": "is in liquid format: {{doc.test}}" } }, "input": { "kind": "inlineDocument", "inline": { "test": true } } } ``` </details> <details><summary>response</summary> ```jsonc { "template": { "json_maps": "supported for fragments", "any_string": "is in liquid format: {{doc.test}}" }, "rendered": { "json_maps": "supported for fragments", "any_string": "is in liquid format: true" } } ``` </details> #### [Experimental] Only support foreign filters on retrieval routes > by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6446](https://github.com/meilisearch/meilisearch/pull/6446) Foreign filters are meant to be used in a retrieval context (search, get document...), but all the actions related to writing or modifying a document could have several unexpected behaviors if foreign filters are accepted. We prefer forbidding the usage of this feature on the writing routes. The following routes do not support Foreign-filter anymore: - [Edit documents by function](https://www.meilisearch.com/docs/reference/api/documents/edit-documents-by-function): POST `/indexes/{index_uid}/documents/edit` - [Delete documents by filter](https://www.meilisearch.com/docs/reference/api/documents/delete-documents-by-filter): POST `/indexes/{index_uid}/documents/delete` - [Export to a remote Meilisearch](https://www.meilisearch.com/docs/reference/api/export/export-to-a-remote-meilisearch): POST `/export` > Additional change: we now ensure that the experimental features are checked when parsing a filter ### 🪲 Bug fixes - Support prefix search on words registered in the disableOnAttributes and disableOnNumbers settings by [@&#8203;antcybersec](https://github.com/antcybersec) in [#&#8203;6432](https://github.com/meilisearch/meilisearch/pull/6432) - Add missing logs in search performance details [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6457](https://github.com/meilisearch/meilisearch/pull/6457) - Ensure the index map budget is a multiplier of the OS page size by [@&#8203;genisis0x](https://github.com/genisis0x) in [#&#8203;6454](https://github.com/meilisearch/meilisearch/pull/6454) ### 🔒 Security - Reduce risk of vulnerability exploits on GHA by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6451](https://github.com/meilisearch/meilisearch/pull/6451) ### **🔩 Miscellaneous** - Replace the `queueDocumentsFetch` experimental feature with `disableDocumentsFetchQueue` converting the feature from an opt-in to an opt-out By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6456](https://github.com/meilisearch/meilisearch/pull/6456) - Bump and removes unused dependencies by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6444](https://github.com/meilisearch/meilisearch/pull/6444) - Fix Ollama embeddings changes to fix CI tests by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6450](https://github.com/meilisearch/meilisearch/pull/6450) ❤️ Thanks again to [@&#8203;genisis0x](https://github.com/genisis0x) and [@&#8203;antcybersec](https://github.com/antcybersec) ### [`v1.47.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.47.1): 🦇 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.47.0...v1.47.1) Meilisearch v1.48.2 and Meilisearch v1.47.1 address CVE-2026-57823 and CVE-2026-57824. We recommend updating if you are in one of the following situations: 1. You have API keys where `indexes` is *not* `["*"]` and where `actions` contains more permissions than: `["search", "documents.*", "indexes.*", "tasks.cancel", "tasks.delete", "tasks.get", "settings.*", "stats.*", "fields.post"]` 2. You have [search tenant tokens](https://www.meilisearch.com/docs/capabilities/security/overview) and either an [embedder](https://www.meilisearch.com/docs/getting_started/glossary#embedder) or a [chat workspace](https://www.meilisearch.com/docs/capabilities/conversational_search/how_to/configure_chat_workspace) - We recommend that users of Meilisearch v1.48 update to Meilisearch v1.48.2 - We recommend that users of Meilisearch v1.47 or lower update to Meilisearch v1.47.1 These versions both fix the following: 1. CVE-2026-57824: Improper authentication leads to privilege escalation: an authenticated user with an index-scoped API and the appropriate set of actions could use global actions to read and write the global state of the Meilisearch instance. Possibly impacted users of Meilisearch Cloud were contacted ahead-of-time. 2. CVE-2026-57823: Improper authentication leads to information disclosure: a user with a search tenant token could get some limited information about the existence of a document outside of the scope of the search rules attached to the tenant token, an indirect information about the content of the document. We detected no trace of exploitation of these vulnerabilities. We thank PuH4ck3rX for reporting these vulnerabilities :heart: ### [`v1.47.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.47.0): 🦇 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.46.1...v1.47.0) ### 🌈 Enhancements #### Search personalization on federated search We now support using the [search personalization feature](https://www.meilisearch.com/docs/capabilities/personalization/overview) on federated search requests. Like `page`/`hitPerPage` or `limit`/`offset`, the personalization option must be specified in the federation attribute to work properly. Otherwise, an error will be returned reminding you to move the attribute in federation. By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6414](https://github.com/meilisearch/meilisearch/pull/6414) #### The new settings indexer is feature complete 🎉 - We now better support the tokenizer-related settings - We improved the quality of the new settings indexer to enhance the engine's performance when changing the locales, the dictionary, synonyms, stop words, separator, and non-separator tokens. - This makes the new settings indexer feature-complete, meaning that, unless you set the `MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS` environment variable to `true`, all settings tasks can now be handled by the new settings indexer, bringing a better scaling behavior, much faster cancellation, and a more precise progress view. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6409](https://github.com/meilisearch/meilisearch/pull/6409) #### Observability improvements We expose more Prometheus metrics to improve observability, specifically to show more metrics on document throughput and ease debugging. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6430](https://github.com/meilisearch/meilisearch/pull/6430) ### 🦋 Fixes - Putting attributeRank/ wordPosition before words in the rankingRules list will no longer remove hits from the response, by [@&#8203;pjdurden](https://github.com/pjdurden) in [#&#8203;6437](https://github.com/meilisearch/meilisearch/pull/6437) - Meilisearch will no longer ignore the `searchCutoffMs` in some conditions when embedding documents, by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6447](https://github.com/meilisearch/meilisearch/pull/6447) - Meilisearch will no longer fail to proxy a search request with a filter containing a `'` during remote federated search or `useNetwork: true` search requests, by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6445](https://github.com/meilisearch/meilisearch/pull/6445) ### 🔒 Security - CI: Prevent shell injection in GitHub Actions release workflows by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6420](https://github.com/meilisearch/meilisearch/pull/6420) ### 🔩 Misc. changes #### Search implementation refactor Refactor the search pipeline to mutualize the code. The new implementation will always perform a federated search under the hood, and then the output will be transformed into the expected route's output. Noticeable changes from the user perspective: - Some error messages have been modified - Small breaking change: a few error codes change, such as `MultiSearch<Error>` <--> `Search<Error>` #### Other changes - Make it easier and less error-prone to declare a type that is used as a body parameter on a Meilisearch endpoint, by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6429](https://github.com/meilisearch/meilisearch/pull/6429) - Remove the now unused `vectorStoreBackend` setting from the settings, by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6399](https://github.com/meilisearch/meilisearch/pull/6399) - Replace custom hf-hub git dependency by the official one by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6442](https://github.com/meilisearch/meilisearch/pull/6442) - Update Python SDK test CI by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6439](https://github.com/meilisearch/meilisearch/pull/6439) - Refactor the code to use the `MustStopProcessing` type everywhere by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6423](https://github.com/meilisearch/meilisearch/pull/6423) #### New Contributors - [@&#8203;pjdurden](https://github.com/pjdurden) made their first contribution in [#&#8203;6437](https://github.com/meilisearch/meilisearch/pull/6437) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.46.1...v1.47.0> ### [`v1.46.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.46.1): 🦆 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.46.0...v1.46.1) #### Queue documents fetch routes Add an experimental feature, `queueDocumentsFetch`, forcing the routes `GET indexes/:uid/documents` and `POST indexes/:uid/documents/fetch` to wait in the search queue if there is no available thread to process them. ### [`v1.46.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.46.0): 🦆 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.45.2...v1.46.0) This release introduces fixes for a regression in v1.45.0, where we were batching deletions by filter with other deletions or additions. It also enables the new settings indexer to support more parameters, making the engine faster to index documents when those settings are specified. ##### ✨ Enhancement - Support exact and disable on numbers in the new settings indexer by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6398](https://github.com/meilisearch/meilisearch/pull/6398) Introduce support for exact words and disable-on-words parameters in the new settings indexer, making the engine more efficient when changing these settings. - Support computing prefixes in the new settings indexer by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6391](https://github.com/meilisearch/meilisearch/pull/6391) Support for the prefix search settings in the new settings indexer, so that changing this parameter makes the engine more efficient. ##### 🪲 Bug fixes - Better limit read bytes when creating the S3 multipart part by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6405](https://github.com/meilisearch/meilisearch/pull/6405) This fixes an issue we had with the multipart part size by ensuring we never construct a part larger than the defined multipart part size. With this fix, we always create a multipart with the provided multipart part size, except for the last part. Thanks, [@&#8203;vidit-virmani](https://github.com/vidit-virmani), for the help investigating the issue. - Batch of `documentDeletionByFilter` with `documentAdditionOrUpdate` by [@&#8203;Kerollmops](https://github.com/Kerollmops) and [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6415](https://github.com/meilisearch/meilisearch/pull/6415) Correctly implement the support for auto-batching deletion by filter with document replacement and updates. This fixes a regression introduced in v1.45.0. - Fix a panic with incomplete filters by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6421](https://github.com/meilisearch/meilisearch/pull/6421) Fixes an internal panic when a filter is incomplete by returning an error instead. ##### 🔒 Security - Bump tar from 0.4.45 to 0.4.46 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6418](https://github.com/meilisearch/meilisearch/pull/6418) ##### 🔩 Miscellaneous - OpenAPI CI: disable rule to avoid crash (workaround) by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6417](https://github.com/meilisearch/meilisearch/pull/6417) - Remove milli benchmarks by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6419](https://github.com/meilisearch/meilisearch/pull/6419) - Add precision in the index swap documentation by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6408](https://github.com/meilisearch/meilisearch/pull/6408) - Fix broken links in the documentation by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6406](https://github.com/meilisearch/meilisearch/pull/6406) ### [`v1.45.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.45.2): 🦒 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.45.1...v1.45.2) ##### 🪲 Bug Fixes - Fix internal vector stores quantization config desync by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6411](https://github.com/meilisearch/meilisearch/pull/6411) We noticed issues when dumpless upgrading databases containing embedders from versions older than v1.33.1. This version fixes those databases by removing the corrupted embeddings from the impacted indexes. **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.45.1...v1.45.2> ### [`v1.45.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.45.1): 🦒 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.45.0...v1.45.1) ##### 🪲 Bug Fixes - Revert autobatch deletions by filter with additions by [@&#8203;kerollmops](https://github.com/kerollmops) in [#&#8203;6412](https://github.com/meilisearch/meilisearch/pull/6412) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.45.0...v1.45.1> ### [`v1.45.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.45.0): 🦒 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.44.0...v1.45.0) Meilisearch v1.45.0 mainly improves indexing performance when changing settings and also improves document fetch performance. ##### ✨ Enhancement - **Autobatch deletions by filter with additions** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6389](https://github.com/meilisearch/meilisearch/pull/6389) While Meilisearch tries to improve indexing speed when users add documents and mix those additions with deletions via a filter, it is still an anti-pattern to interleave both. It is recommended to delete documents by ID whenever possible, as the engine is optimized to merge them, thereby drastically speeding up indexation. - **Improve settings indexing performance & visibility** We are introducing support for more settings in the nez settings indexer. If you find any bugs, please report them on GitHub. You can disable the new settings indexer by setting the environment variable like this: `MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS=true` or use the equivalent dedicated CLI parameter. - **Support non-extracting parameters** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6393](https://github.com/meilisearch/meilisearch/pull/6393) Changing one of the following settings is now directly handled by the new settings indexer: displayed fields, synonyms, the primary key, authorize typos, min word len one and two typos, max values per facet, sort facet values by, pagination max total hits, search cut off, chat, and foreign keys. - **Support the global facet search** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6390](https://github.com/meilisearch/meilisearch/pull/6390) Meilisearch can use the new settings indexer when the settings change the facet search root boolean parameter. ##### 🪲 Bug Fixes - **Fetching documents no longer blocks the actix worker** [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6402](https://github.com/meilisearch/meilisearch/pull/6402) - **Fix an internal error when changing the binary quantization** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6396](https://github.com/meilisearch/meilisearch/pull/6396) We fixed an issue where users were changing the binary-quantized boolean in embedder configurations. The change corrupted the database, making it impossible to change the quantization in the future. Users had to create a binary-quantized embedder from scratch, or they could never change it again. ##### 🔩 Miscellaneous - Make timeout test less flaky on Windows by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6388](https://github.com/meilisearch/meilisearch/pull/6388) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.44.0...v1.45.0> ### [`v1.44.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.44.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.43.1...v1.44.0) Meilisearch v1.44.0 adds remote federated facet search, indexing performance improvements, and other improvements and bugfixes. It also contains a couple of breaking changes, detailed below. ### Breaking changes - When using the `network` experimental feature, with sharding enabled (`leader` is not `null` in the network configuration), `POST /indexes/{indexUid}/facet-search` calls now default to a remote federated facet search, fetching and merging results from all shards in the network. - The timeout for calling an external REST embedder at search time is now tied to the `searchCutOffMs` defined in the index, rather than fixed. - If you observe missing semantic results after upgrading, or HTTP 500 errors for pure semantic search, please increase the value of the search cutoff in the index settings. - By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6377](https://github.com/meilisearch/meilisearch/pull/6377) ### 🌈 Improvements #### Remote facet search Meilisearch now has the ability to search across all shards of a network during facet search via the existing dedicated facet search route. - If you are using the `network` experimental feature and have a `leader` defined for your network, **remote calls are now the default** for calls to `POST /indexes/{indexUid}/facet-search` - The behavior can be controlled explicitly via the new `useNetwork` parameter of the [facet search object](https://www.meilisearch.com/docs/reference/api/facet-search/search-in-facets#body-facet-name). By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6375](https://github.com/meilisearch/meilisearch/pull/6375) #### Reduce memory usage of the indexing Reduces allocated memory when computing prefixes and speeds up some operations to avoid unnecessary deserialization. If you still see high memory usage while the engine is post-processing, we recommend using the `--experimental-reduce-indexing-memory-usage` option. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6334](https://github.com/meilisearch/meilisearch/pull/6334) #### Improve GeoJSON indexing performance This PR upgrades the `cellulite` library to a version that includes a GeoJSON indexing optimization. With this change, GeoJSON indexing avoids reprocessing documents that were already indexed in dense cells, and only handles newly added documents incrementally as they descend through the recursive cell tree. By [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6374](https://github.com/meilisearch/meilisearch/pull/6374) #### Human-formatted sizes and detailed DB sizes in stats Adds two new query parameters to `GET /indexes/{indexUid}/stats` and `GET /stats`: - `showInternalDatabaseSizes`: boolean, optional, defaults to `false`. When present, the index stat objects in responses of the stat routes now contain an additional `internalDatabaseSizes` key, whose value is a dictionary of the internal database names and their current size in the index, like in the stats object of a batch. - `sizeFormat`: `human` or `raw`: optional, defaults to `raw`. When present and set to `human`, then all database sizes in responses of the stat routes will be returned as a string containing an appropriate unit (MiB, GiB, etc). When missing or set to `raw`, then the current behavior of expressing the size in bytes as a number is retained. Note for integrations: The keys in `internalDatabaseSizes` are subject to change and should not be exposed as a strongly typed object. This is the same as the existing `internalDatabaseSizes` in batch stats. <details> <summary> Adding `showInternalDatabaseSizes` to an index stats </summary> ```jsonc // curl -X GET "http://localhost:7700/indexes/movies/stats?showInternalDatabaseSizes=true" { "numberOfDocuments": 31944, "rawDocumentDbSize": 20594688, "avgDocumentSize": 636, "isIndexing": false, "internalDatabaseSizes": { "wordPairProximityDocids": 100827136, "documents": 20594688, "wordPositionDocids": 18694144, "wordFidDocids": 10715136, "wordPrefixPositionDocids": 10256384, "wordDocids": 9453568, "wordPrefixFidDocids": 4603904, "wordPrefixDocids": 3424256, "main": 1425408, "externalDocumentsIds": 999424, "fieldIdWordCountDocids": 245760, "exactWordPrefixDocids": 16384, "celluliteMetadata": 16384 }, "numberOfEmbeddings": 0, "numberOfEmbeddedDocuments": 0, "fieldDistribution": { "genres": 31944, "id": 31944, "overview": 31944, "poster": 31944, "release_date": 31944, "title": 31944 } } ``` </details> <details> <summary> Adding `showInternalDatabaseSizes` and `sizeFormat=human` to global stats </summary> ```jsonc // curl -X GET "http://localhost:7700/stats?showInternalDatabaseSizes=true&sizeFormat=human" { "databaseSize": "351.38 MiB", "usedDatabaseSize": "350.64 MiB", "lastUpdate": "2026-04-16T13:07:02.74243Z", "indexes": { "comics": { "numberOfDocuments": 31944, "rawDocumentDbSize": "23.14 MiB", "avgDocumentSize": "751 B", "isIndexing": false, "internalDatabaseSizes": { "wordPairProximityDocids": "98.06 MiB", "documents": "23.14 MiB", "wordPositionDocids": "17.22 MiB", "wordFidDocids": "10.36 MiB", "wordPrefixPositionDocids": "9.47 MiB", "wordDocids": "8.97 MiB", "wordPrefixFidDocids": "4.36 MiB", "wordPrefixDocids": "3.27 MiB", "main": "1.36 MiB", "externalDocumentsIds": "944 KiB", "fieldIdWordCountDocids": "240 KiB", "exactWordPrefixDocids": "16 KiB", "celluliteMetadata": "16 KiB" }, "numberOfEmbeddings": 0, "numberOfEmbeddedDocuments": 0, "fieldDistribution": { "genres": 31944, "id": 31944, "overview": 31944, "poster": 31944, "release_date": 31944, "title": 31944 } }, "movies": { "numberOfDocuments": 31944, "rawDocumentDbSize": "19.64 MiB", "avgDocumentSize": "636 B", "isIndexing": false, "internalDatabaseSizes": { "wordPairProximityDocids": "96.16 MiB", "documents": "19.64 MiB", "wordPositionDocids": "17.83 MiB", "wordFidDocids": "10.22 MiB", "wordPrefixPositionDocids": "9.78 MiB", "wordDocids": "9.02 MiB", "wordPrefixFidDocids": "4.39 MiB", "wordPrefixDocids": "3.27 MiB", "main": "1.36 MiB", "externalDocumentsIds": "976 KiB", "fieldIdWordCountDocids": "240 KiB", "exactWordPrefixDocids": "16 KiB", "celluliteMetadata": "16 KiB" }, "numberOfEmbeddings": 0, "numberOfEmbeddedDocuments": 0, "fieldDistribution": { "genres": 31944, "id": 31944, "overview": 31944, "poster": 31944, "release_date": 31944, "title": 31944 } } } } ``` </details> <details> <summary> The call without any parameters is the same as in previous versions. </summary> ```jsonc // curl -X GET "http://localhost:7700/stats" { "databaseSize": 368443392, "usedDatabaseSize": 367673344, "lastUpdate": "2026-04-16T13:07:02.74243Z", "indexes": { "comics": { "numberOfDocuments": 31944, "rawDocumentDbSize": 24264704, "avgDocumentSize": 751, "isIndexing": false, "numberOfEmbeddings": 0, "numberOfEmbeddedDocuments": 0, "fieldDistribution": { "genres": 31944, "id": 31944, "overview": 31944, "poster": 31944, "release_date": 31944, "title": 31944 } }, "movies": { "numberOfDocuments": 31944, "rawDocumentDbSize": 20594688, "avgDocumentSize": 636, "isIndexing": false, "numberOfEmbeddings": 0, "numberOfEmbeddedDocuments": 0, "fieldDistribution": { "genres": 31944, "id": 31944, "overview": 31944, "poster": 31944, "release_date": 31944, "title": 31944 } } } } ``` </details> By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6338](https://github.com/meilisearch/meilisearch/pull/6338) ### 🦋 Fixes - Settings changes performed via a settings subroute (**not** the ["all settings" route](https://www.meilisearch.com/docs/reference/api/settings/update-all-settings)) are now correctly propagated to other remotes on the network. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6380](https://github.com/meilisearch/meilisearch/pull/6380) - The chat route no longer fails in some condition when using Mistral as a provider. By [@&#8203;renezander030](https://github.com/renezander030) in [#&#8203;6327](https://github.com/meilisearch/meilisearch/pull/6327) - Prevent accidentally renaming a remote when modifying the network configuration. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6370](https://github.com/meilisearch/meilisearch/pull/6370) ### 🔩 Miscellaneous changes - Replace boolean by PatternMatch for searchable by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6344](https://github.com/meilisearch/meilisearch/pull/6344) - Add query to federated search metadata by [@&#8203;StephaneRob](https://github.com/StephaneRob) in [#&#8203;6371](https://github.com/meilisearch/meilisearch/pull/6371) - Remove issue template for feature issues by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6372](https://github.com/meilisearch/meilisearch/pull/6372) - Improve the documentation of the health route by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6376](https://github.com/meilisearch/meilisearch/pull/6376) #### New Contributors - [@&#8203;renezander030](https://github.com/renezander030) made their first contribution in [#&#8203;6327](https://github.com/meilisearch/meilisearch/pull/6327) - [@&#8203;quyentonndbs](https://github.com/quyentonndbs) made their first contribution in [#&#8203;6382](https://github.com/meilisearch/meilisearch/pull/6382) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.43.1...v1.44.0> ### [`v1.43.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.43.1) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.43.0...v1.43.1) Meilisearch v1.43.1 contains a security fix for an authenticated SSRF vulnerability. No exploitation was found on Meilisearch Cloud. Cloud users are not required to update. We recommend that self-hosting users upgrade if they allow third parties to configure Meilisearch instances. We thank Sion Park ([@&#8203;tldhs1144](https://github.com/tldhs1144)), who reported the issue and suggested a fix, for improving the security of Meilisearch ❤️ ### [`v1.43.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.43.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.42.1...v1.43.0) ### 🌈 Enhancements #### New settings indexer The new settings indexer, a more efficient version of our internal indexer for index settings modifications, now supports filterable, sortable, facet search, and custom (asc/desc) attributes in addition to the already-supported searchable, exact, proximity precision, and embedders. - For Meilisearch Cloud users, the new settings indexer is disabled by default and can be enabled on a case-by-case basis for scaling purposes. - For OSS users, the new settings indexer can be disabled by setting the `MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS` to `true`. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6124](https://github.com/meilisearch/meilisearch/pull/6124) #### Improve facet search indexing performance We reduced the time to generate the internal data structures for the facet search to work. We were previously doing a couple of full scans on the internal entries and replaced these with scans on specific entries, only the ones dedicated to the facet searchable fields. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6325](https://github.com/meilisearch/meilisearch/pull/6325) #### Improve task queue compaction integration The `GET /health` route now returns HTTP 500 after a successful task queue compaction, to signal that Meilisearch should be restarted so that tasks can be enqueued again. For Meilisearch Cloud users, this ensures that compacting the task queue will automatically restart the instance after the compaction. ### 🦋 Fixes #### Fix lexicographic filters on strings Fixes a bug where string facet values appearing in `<, <=, >, >=` and `IN` filters were not normalized before comparison to facet values. This would cause some values in documents (e.g. `2026-01-01T00:00:00`) to appear to be higher than their filter counterpart, due to being normalized (e.g. like `2026-01-01t00:00:00`). Thanks to [@&#8203;njaard](https://github.com/njaard) for [reporting the issue](https://github.com/meilisearch/meilisearch/issues/6335) ❤️ By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6340](https://github.com/meilisearch/meilisearch/pull/6340) #### Fix typo tolerance v1.41 regression Fixes the `WordDelta::added_or_deleted_words` function. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6350](https://github.com/meilisearch/meilisearch/pull/6350). Thanks to [@&#8203;vladradin99](https://github.com/vladradin99) and [@&#8203;snurfer0](https://github.com/snurfer0) for reporting the issue in [#&#8203;6349](https://github.com/meilisearch/meilisearch/issues/6349) and [#&#8203;6324](https://github.com/meilisearch/meilisearch/issues/6324) :heart: ### 🔩 Miscellaneous - Introduce a meilitool command to export an index words FST by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6332](https://github.com/meilisearch/meilisearch/pull/6332) - Add riscv64 to release binary matrix via cross-rs by [@&#8203;gounthar](https://github.com/gounthar) in [#&#8203;6296](https://github.com/meilisearch/meilisearch/pull/6296) - Fix docs related to task cancelation and deletion by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6353](https://github.com/meilisearch/meilisearch/pull/6353) - Bump actions/checkout from 5 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6303](https://github.com/meilisearch/meilisearch/pull/6303) - Bump actions/setup-node from 4 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5964](https://github.com/meilisearch/meilisearch/pull/5964) - Bump thin-vec from 0.2.14 to 0.2.16 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6339](https://github.com/meilisearch/meilisearch/pull/6339) - Bump docker/setup-buildx-action from 3 to 4 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6304](https://github.com/meilisearch/meilisearch/pull/6304) - Bump rustls-webpki from 0.103.10 to 0.103.13 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6347](https://github.com/meilisearch/meilisearch/pull/6347) - Bump actix-http from 3.11.2 to 3.12.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6348](https://github.com/meilisearch/meilisearch/pull/6348) - Bump sigstore/cosign-installer from 3.10.0 to 4.1.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6301](https://github.com/meilisearch/meilisearch/pull/6301) - Bump supercharge/mongodb-github-action from 1.12.0 to 1.12.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6302](https://github.com/meilisearch/meilisearch/pull/6302) Thanks again [@&#8203;gounthar](https://github.com/gounthar), [@&#8203;njaard](https://github.com/njaard), [@&#8203;vladradin99](https://github.com/vladradin99) and [@&#8203;snurfer0](https://github.com/snurfer0) for your contributions ❤️ **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.42.1...v1.43.0> ### [`v1.42.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.42.1): 🦑​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.42.0...v1.42.1) #### 🪲 Bug fixes ##### Fix issues when using the legacy settings indexer By [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6331](https://github.com/meilisearch/meilisearch/pull/6331) - When using the experimental feature "multimodal", removing a fragment would cause an internal error in subsequent search requests - When using the experimental feature "multimodal", modifying fragments would sometimes cause an internal error at indexing time - `regenerate: false` would be ignored when modifying embedder settings - When a nested field was declared as searchable, it would not be indexed if its parents were not declared as searchable #### 🔩 Miscellaneous - Add new CI run that tests the stable settings indexer by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6331](https://github.com/meilisearch/meilisearch/pull/6331) ### [`v1.42.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.42.0): 🦑​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.41.0...v1.42.0) ### **✨ Enhancement** #### Support search fallback on remote unavailability By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6306](https://github.com/meilisearch/meilisearch/pull/6306) We introduce a new fallback system for the sharding and replication enterprise edition feature, along with a way to determine which remote is available. The engine can avoid machines that are unavailable for a period and resume querying them once they're back online. The following snippet shows what the /network route looks like now that this PR exposes the remote statuses/availabilities. ```json "remotes": { "prod2": { "url": "http://localhost:7702", "searchApiKey": "mykey", "writeApiKey": "mykey", "status": "available" }, "prod3": { "url": "http://localhost:7703", "searchApiKey": "mykey", "writeApiKey": "mykey", "status": "unavailable" } } ``` #### 🔬 Experimental: Document join Filtering By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6314](https://github.com/meilisearch/meilisearch/pull/6314) This enhancement extends the `Cross-index document hydration introduced` in [v1.39.0](https://github.com/meilisearch/meilisearch/releases/tag/v1.39.0) by allowing the user to filter on the foreign indexes to retrieve the documents. > 📓 Note: This implementation doesn't support a remote sharding environment ##### `foreignKeys` experimental feature The`foreignKeys` experimental feature must be activated to use the foreign filters: ``` curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \ -H 'Content-Type: application/json' \ --data-binary '{"foreignKeys": true}' ``` ##### `foreignKeys` + `filter` index setting To be able to use the foreign filters, the related field must be set as a foreignKey and as a filterableAttribute in `/indexes/{index_uid}/settings`: ```jsonc { // new setting, an array of foreign keys that allows multiple foreign relationships between indexes "foreignKeys": [ { // the path in the JSON document containing foreign document ids "fieldName": "actors", // the UID of the foreign index containing the documents to fetch during hydration "foreignIndexUid": "actors" } ], // the actors field must be filterable on equality "filterableAttributes": [ { "attributePatterns": ["actors"], "features": { "facetSearch": false, "filter": { "equality": true, "comparison": false } } } ] } ``` ##### filtering using the `_foreign` filter On the search route, a new `_foreign` verb has been introduced and should be used as follows: ```jsonc { "q": "<query>", // filters on the movie index: // genres = action // AND // the foreign documents from the actor index match: birthday STARTS WITH \"1958-\" AND popularity >= 3.5 "filter": "genres = action AND _foreign(actors, birthday STARTS WITH \"1958-\" AND popularity >= 3.5)" } ``` > Note: nesting foreign filters is not supported and will return an error <details> <summary> ##### Example of usage </summary> ##### Prerequisites - Meilisearch running on `127.0.0.1:7700` on the `document-join-hydration` branch. ##### Step 1: Enable Foreign Keys Feature ```bash curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \ -H 'Content-Type: application/json' \ --data-binary '{"foreignKeys": true}' ``` ##### Step 2: Create Indexes ##### Create the `actors` index ```bash curl -X POST 'http://127.0.0.1:7700/indexes' \ -H 'Content-Type: application/json' \ --data-binary '{"uid": "actors", "primaryKey": "id"}' ``` ##### Create the `movies` index ```bash curl -X POST 'http://127.0.0.1:7700/indexes' \ -H 'Content-Type: application/json' \ --data-binary '{"uid": "movies", "primaryKey": "id"}' ``` ##### Step 3: Add Documents to the `actors` Index ```bash curl -X POST 'http://127.0.0.1:7700/indexes/actors/documents' \ -H 'Content-Type: application/json' \ --data-binary '[ {"id": 1, "name": "Tom", "familyName": "Hanks", "birthDate": "1956-07-09"}, {"id": 2, "name": "Meryl", "familyName": "Streep", "birthDate": "1949-06-22"}, {"id": 3, "name": "Leonardo", "familyName": "DiCaprio", "birthDate": "1974-11-11"}, {"id": 4, "name": "Emma", "familyName": "Watson", "birthDate": "1990-04-15"} ]' ``` ##### Step 4: Add Documents to the `movies` Index ```bash curl -X POST 'http://127.0.0.1:7700/indexes/movies/documents' \ -H 'Content-Type: application/json' \ --data-binary '[ {"id": 1, "title": "Forrest Gump", "description": "The presidencies of Kennedy and Johnson, the Vietnam War, the Watergate scandal and other historical events unfold from the perspective of an Alabama man with an IQ of 75.", "actors": [1]}, {"id": 2, "title": "The Devil Wears Prada", "description": "A smart but sensible new graduate lands a job as an assistant to Miranda Priestly, the demanding editor-in-chief of a high fashion magazine.", "actors": [2, 4]}, {"id": 3, "title": "Inception", "description": "A thief who steals corporate secrets through the use of dream-sharing technology is given the inverse task of planting an idea into the mind of a C.E.O.", "actors": [3]}, {"id": 4, "title": "Cast Away", "description": "A FedEx executive undergoes a physical and emotional transformation after crash landing on a deserted island.", "actors": [1]} ]' ``` ##### Step 5: Configure Foreign Keys on the `movies` Index ```bash curl -X PATCH 'http://127.0.0.1:7700/indexes/movies/settings' \ -H 'Content-Type: application/json' \ --data-binary '{"foreignKeys": [{"fieldName": "actors", "foreignIndexUid": "actors"}], "filterableAttributes": [{"attributePatterns": ["actors"],"features": {"facetSearch": false,"filter": {"equality": true,"comparison": false}}}]}' ``` ##### Step 6: Configure filterable on the `actors` Index ```bash curl -X PATCH 'http://127.0.0.1:7700/indexes/actors/settings' \ -H 'Content-Type: application/json' \ --data-binary '{"filterableAttributes": [{"attributePatterns": ["birthDate"],"features": {"facetSearch": false,"filter": {"equality": true,"comparison": false}}}]}' ``` ##### Step 7: Perform a Federated Search ```bash curl -X POST 'http://127.0.0.1:7700/multi-search' \ -H 'Content-Type: application/json' \ --data-binary '{ "queries": [ { "indexUid": "movies", "q": "Forrest", "filter": "_foreign(actors, birthDate = \"1956-07-09\")" } ], "federation": { "limit": 20, "offset": 0 } }' ``` ##### Expected Result The federated search should return movie documents with the `actors` array automatically hydrated with full actor objects instead of just IDs: ```json { "hits": [ { "id": 1, "title": "Forrest Gump", "description": "...", "actors": [ { "id": 1, "name": "Tom", "familyName": "Hanks", "birthDate": "1956-07-09" } ], "_federation": { "indexUid": "movies", "queriesPosition": 0, "weightedRankingScore": 0.9848484848484849 } } ], "processingTimeMs": 208, "limit": 20, "offset": 0, "estimatedTotalHits": 1 } ``` </details> ### 🪲 Bug fixes - Fix a race condition when writing network by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6300](https://github.com/meilisearch/meilisearch/pull/6300) We fixed a race condition in network topology changes that could cause errors and prevent documents from being correctly indexed. Additionally, we fixed a bug in the `networkTopologyChange` task batching that was causing it to batch too many task types. We made sure it only batches import tasks, and only those, to avoid out-of-order task processing. - Throw document template errors when updating the chat settings by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6321](https://github.com/meilisearch/meilisearch/pull/6321) We fixed an issue that prevented the engine from explicitly showing the possible document template errors users could encounter when updating the template in the chat settings. The engine now correctly checks for and throws template errors when they are detected. - Fix: Update Index tasks will be properly forwarded to remote nodes by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6299](https://github.com/meilisearch/meilisearch/pull/6299) - Fix action mistake on the chat completions route by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6290](https://github.com/meilisearch/meilisearch/pull/6290) ### **🔩 Miscellaneous** - Use the latest version of heed with nested rtxns support by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6316](https://github.com/meilisearch/meilisearch/pull/6316) This PR bumps the versions of crates that use heed to [the latest version, v0.22.1](https://github.com/meilisearch/heed/releases/tag/v0.22.1). This version finally stabilized a long-standing piece of work we were doing with Howard Chu: nested read transactions. We no longer have to rely on unstable pre-releases, but rather on a clean, stable version of LMDB (still a fork, but a better one). - Add section to [CONTRIBUTING.md](http://contributing.md/) to bump mini-dashboard version and testing section to right place by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6195](https://github.com/meilisearch/meilisearch/pull/6195) - Make the no-agent [AGENTS.ms](http://agents.ms/) more permissive by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6260](https://github.com/meilisearch/meilisearch/pull/6260) - Remove deleted test commands by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6283](https://github.com/meilisearch/meilisearch/pull/6283) - Fix OpenAPI schema generation for chat completions route by [@&#8203;qdequele](https://github.com/qdequele) in [#&#8203;6274](https://github.com/meilisearch/meilisearch/pull/6274) - Rename OpenAPI route names for search rules and compact by [@&#8203;qdequele](https://github.com/qdequele) in [#&#8203;6298](https://github.com/meilisearch/meilisearch/pull/6298) - Update README with new features and demos by [@&#8203;qdequele](https://github.com/qdequele) in [#&#8203;6297](https://github.com/meilisearch/meilisearch/pull/6297) - Prevent shell injection in benchmark workflows by [@&#8203;curquiza](https://github.com/curquiza) & [@&#8203;Kerollmopsin](https://github.com/Kerollmopsin) [#&#8203;6308](https://github.com/meilisearch/meilisearch/pull/6308) & [#&#8203;6318](https://github.com/meilisearch/meilisearch/pull/6318) - Rename some of the search performance traces by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6323](https://github.com/meilisearch/meilisearch/pull/6323) ### [`v1.41.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.41.0): 🏈 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.40.0...v1.41.0) ##### ✨ Enhancement - **Support dynamic search rules with pinning** by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6182](https://github.com/meilisearch/meilisearch/pull/6182) Introduce the Dynamic Search Rules (DSR) experimental feature, making it easy to promote the right content for the right searches with flexible, condition-based pinning. In this first version, rules can be triggered by query-based conditions such as empty queries or literal substring matches, as well as time windows. Multiple documents can be pinned in a defined order, and pins still work with filtering, pagination, facet distribution, hybrid search, and federated search. This feature is behind the `dynamicSearchRules` experimental feature flag. Rules can be created or updated with `PATCH /dynamic-search-rules/{uid}` and removed with `DELETE /dynamic-search-rules/{uid}`. In this first version, a rule can define query- or time-based conditions and pin specific documents at fixed positions in the results list. <details> <summary>Example of rule creation/update</summary> ``` // PATCH /dynamic-search-rules/featured-wireless-headphones { "description": "Promote featured products for wireless headphone searches", "active": true, "conditions": [ { "scope": "query", "contains": "headphone" } ], "actions": [ { "selector": { "indexUid": "products", "id": "featured-headphones-001" }, "action": { "type": "pin", "position": 0 } }, { "selector": { "indexUid": "products", "id": "featured-headphones-002" }, "action": { "type": "pin", "position": 1 } } ] } ``` </details> - **Default to `useNetwork: true` in sharded instances by** [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6278](https://github.com/meilisearch/meilisearch/pull/6278) > This release contains [**breaking changes**](#search-requests-breaking-changes) for users of the `network` experimental feature. ##### Search requests now use the network by default when (replicated) sharding is enabled ##### <a id="search-requests-breaking-changes">§</a> Breaking changes When `network.leader` is set in the instance, `useNetwork` now defaults to `true` in search requests when omitted. So, when a network is configured, the following: <details> <summary>Search request without an explicit useNetwork</summary> ```jsonc // POST /indexes/movies/search { "q": "Batman dark knight returns 1", "filter": "genres IN [Action, Adventure]", "facets": ["genres"], "limit": 5 // No `useNetwork` is passed } ``` </details> is now equivalent to a federated search over multiples remotes so that all shards in the network are covered exactly once. <details> <summary>Equivalent federated search request</summary> ```jsonc // POST /multi-search { "federation": { "limit": 5, "facetsByIndex": { "movies": [ "genres" ] }, "merge": {} }, // assuming 3 remotes 0, 1, 2 and 3 shards a, b, c such that // 0 owns a, b // 1 owns b, c // 2 owns c, a "queries": [ { "indexUid": "movies", "federationOptions": { "remote": "0" }, "q": "Batman dark knight returns 1", "filter": ["genres IN [Action, Adventure]", "_shard = a"] }, { "indexUid": "movies", "federationOptions": { "remote": "0" // useNetwork picked remote 0 for both shard a and b }, "q": "Batman dark knight returns 1", "filter": ["genres IN [Action, Adventure]", "_shard = b"] }, { "indexUid": "movies", "federationOptions": { "remote": "2" }, "q": "Batman dark knight returns 1", "filter": ["genres IN [Action, Adventure]", "_shard = c"] } ] } ``` </details> Responding with documents from all the shards: <details> <summary>Response</summary> ```jsonc { "hits": [ { "id": 123025, "title": "Batman: The Dark Knight Returns, Part 1", "overview": "Batman has not been seen for ten years. A new breed of criminal ravages Gotham City, forcing 55-year-old Bruce Wayne back into the cape and cowl. But, does he still have what it takes to fight crime in a new era?", "genres": [ "Action", "Animation", "Mystery" ], "poster": "https://image.tmdb.org/t/p/w500/kkjTbwV1Xnj8wBL52PjOcXzTbnb.jpg", "release_date": 1345507200, "_federation": { "indexUid": "mieli", "queriesPosition": 2, "weightedRankingScore": 0.9894586894586894, "remote": "2" } }, { "id": 142061, "title": "Batman: The Dark Knight Returns, Part 2", "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city. Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.", "genres": [ "Action", "Animation", "Mystery" ], "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg", "release_date": 1357171200, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.9894558963186414, "remote": "0" } }, { "id": 16234, "title": "Batman Beyond: Return of the Joker", "overview": "The Joker is back with a vengeance, and Gotham's newest Dark Knight needs answers as he stands alone to face Gotham's most infamous Clown Prince of Crime.", "genres": [ "Animation", "Family", "Action", "Science Fiction" ], "poster": "https://image.tmdb.org/t/p/w500/7RlBs0An83fqAuKfwH5gKMcqgMc.jpg", "release_date": 976579200, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.9427964918160996, "remote": "0" } }, { "id": 155, "title": "The Dark Knight", "overview": "Batman raises the stakes in his war on crime. With the help of Lt. Jim Gordon and District Attorney Harvey Dent, Batman sets out to dismantle the remaining criminal organizations that plague the streets. The partnership proves to be effective, but they soon find themselves prey to a reign of chaos unleashed by a rising criminal mastermind known to the terrified citizens of Gotham as the Joker.", "genres": [ "Drama", "Action", "Crime", "Thriller" ], "poster": "https://image.tmdb.org/t/p/w500/qJ2tW6WMUDux911r6m7haRef0WH.jpg", "release_date": 1216166400, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.5784178187403994, "remote": "0" } }, { "id": 49026, "title": "The Dark Knight Rises", "overview": "Following the death of District Attorney Harvey Dent, Batman assumes responsibility for Dent's crimes to protect the late attorney's reputation and is subsequently hunted by the Gotham City Police Department. Eight years later, Batman encounters the mysterious Selina Kyle and the villainous Bane, a new terrorist leader who overwhelms Gotham's finest. The Dark Knight resurfaces to protect a city that has branded him an enemy.", "genres": [ "Action", "Crime", "Drama", "Thriller" ], "poster": "https://image.tmdb.org/t/p/w500/vzvKcPQ4o7TjWeGIn0aGC9FeVNu.jpg", "release_date": 1342396800, "_federation": { "indexUid": "mieli", "queriesPosition": 2, "weightedRankingScore": 0.5772657450076805, "remote": "2" } } ], "query": "Batman dark knight returns 1", "processingTimeMs": 173, "limit": 5, "offset": 0, "estimatedTotalHits": 47, "facetDistribution": { "genres": { "Action": 46, "Adventure": 15, "Animation": 34, "Comedy": 3, "Crime": 14, "Drama": 6, "Family": 15, "Fantasy": 8, "Horror": 1, "Mystery": 4, "Romance": 1, "Science Fiction": 14, "TV Movie": 4, "Thriller": 4, "Western": 1 } }, "facetStats": {}, "requestUid": "019bbcf4-a609-7701-8d82-d370611adfb3", "remoteErrors": {} } ``` </details> This change allows to naturally query all the documents in a sharded context. When `network.leader` is not present (in particular, when no `network` was defined), then the behavior is identical to previous versions. - **`useNetwork` picks local instance if it owns the shard** by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6287](https://github.com/meilisearch/meilisearch/pull/6287) To prevent unnecessary network activity, when deciding which remote to ask for a shard in a search over the network, Meilisearch will now always pick the local instance if it owns the shard. - **More efficient FST building** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6279](https://github.com/meilisearch/meilisearch/pull/6279) It improves the construction of the word FST (word dictionary) by removing the need for a full scan of the word docids database. This should drastically improve the database's performance when inserting a large number of documents, even when inserting only a few. ##### 🪲 Bug fixes - Handle empty VERSION file as missing by [@&#8203;themavik](https://github.com/themavik) in [#&#8203;6275](https://github.com/meilisearch/meilisearch/pull/6275) ##### 🔩 Miscellaneous - Remap post processing targets for better benchmark readability by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6285](https://github.com/meilisearch/meilisearch/pull/6285) - Update the description of the get task's document payload route by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6284](https://github.com/meilisearch/meilisearch/pull/6284) #### New Contributors - [@&#8203;themavik](https://github.com/themavik) made their first contribution in [#&#8203;6275](https://github.com/meilisearch/meilisearch/pull/6275) ### [`v1.40.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.40.0): 🦈 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.39.0...v1.40.0) This release introduced support for the `distinct` attribute in federated search, enabling cross-index distinct attributes with facet distribution support. Additionally, significant performance improvements were delivered, including faster federated search (approximately 100ms faster), optimized JSON document generation for better handling of large documents and a much better memory usage for large workloads. ##### ✨ Enhancement - **Support `distinct` in federated search** by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6214](https://github.com/meilisearch/meilisearch/pull/6214) The `distinct` attribute can now be passed to the `federation` object in federated search to apply a global, cross-index and cross-remote distinct computation to the results. <details> <summary>Example of a federated search request with distinct</summary> ```json { "federation": { "distinct": "genres", // ✨ NEW "facetsByIndex": { // recovering facet distribution is also supported with distinct "comics": [ "genres" ], "movies": [ "genres" ] }, "mergeFacets": {} // merging facet distributions is also supported with distinct }, "queries": [ { "indexUid": "comics", "q": "batman", "attributesToRetrieve": ["title", "genres"], "useNetwork": true // distinct is also supported with network queries }, { "indexUid": "movies", "q": "superman", "attributesToRetrieve": ["title", "genres"], "useNetwork": true } ] } ``` </details> <details> <summary>Sample response to a federated search request with distinct</summary> ```json { "hits": [ { "title": "Batman", "genres": [ "Family", "Adventure", "Comedy", "Science Fiction", "Crime" ], "_federation": { "indexUid": "comics", "queriesPosition": 0, "weightedRankingScore": 1.0, "remote": "ms2" } }, { "title": "Batman", "genres": [ "Fantasy", "Action" ], "_federation": { "indexUid": "comics", "queriesPosition": 0, "weightedRankingScore": 1.0, "remote": "ms1" } }, { "title": "Batman & Bill", "genres": [ "Documentary" ], "_federation": { "indexUid": "comics", "queriesPosition": 0, "weightedRankingScore": 0.9848484848484848, "remote": "ms1" } }, { "title": "Superman: Red Son", "genres": [], "_federation": { "indexUid": "movies", "queriesPosition": 1, "weightedRankingScore": 0.9848484848484849, "remote": "ms0" } }, { "title": "Superman, Spider-Man or Batman", "genres": [ "Drama" ], "_federation": { "indexUid": "movies", "queriesPosition": 1, "weightedRankingScore": 0.9848484848484849, "remote": "ms0" } } ], "processingTimeMs": 15, "limit": 5, "offset": 0, "estimatedTotalHits": 11, "facetDistribution": { "genres": { "Action": 1, "Adventure": 1, "Comedy": 3, "Crime": 2, "Documentary": 1, "Drama": 1, "Family": 1, "Fantasy": 1, "Horror": 2, "Romance": 1, "Science Fiction": 1, "Thriller": 1, "Western": 1 } }, "facetStats": {}, "requestUid": "019d05c7-ea65-77a1-8274-22a8ba9e26db", "remoteErrors": {} } ``` </details> Note the following to apply the distinct attribute at the federation level: 1. Applying `distinct` at the query level at the same time as the federation level is disallowed and will return a HTTP 400 error. 2. The chosen distinct field will apply to all remotes and indexes, so it must be a filterable attribute for all participating remotes and indexes. 3. While Meilisearch attempts to compute the most accurate facet distribution, in distributed contexts this cannot be guaranteed as the distinct algorithm is not applied on all of the remote documents. - **Improve performance of federated search** by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6229](https://github.com/meilisearch/meilisearch/pull/6229) Improves performance of federated search: about 100ms faster for all requests. Improves reliability of the HTTP server: the server will no longer be blocked when too many federated search requests are being processed. - **Optimize the generation of JSON documents** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6257](https://github.com/meilisearch/meilisearch/pull/6257) Addresses performance issues that users might encounter when requesting large documents. Additionally, performance is enhanced when users request only a small subset of fields from large documents. - **Use the latest version of mimalloc to improve memory usage** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6201](https://github.com/meilisearch/meilisearch/pull/6201) Updates mimalloc from v2 to v3, improving memory sharing between threads and significantly reducing memory usage on large workloads. It also overrides the allocator to use mimalloc at linking time, allowing LMDB, Meilisearch, and other C libraries to share their allocations for better overall memory efficiency. [@&#8203;Kerollmops](https://github.com/Kerollmops) wrote [a blog post about the story behind this improvement](https://blog.kerollmops.com/the-good-the-bad-and-the-leaky-jemalloc-bumpalo-and-mimalloc-in-meilisearch). - **Add `POST /tasks/compact` for task queue compaction** by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6193](https://github.com/meilisearch/meilisearch/pull/6193) Compacts the task queue database and reclaim space so new tasks can keep being enqueued, without deleting existing tasks. This feature is behind the `taskQueueCompactionRoute` experimental feature flag. > \[!WARNING]\ > Once task queue compaction completes, all write operations are blocked until the server is restarted. ##### 🔐 Security - Bump rustls-webpki from 0.103.8 to 0.103.10 in [#&#8203;6273](https://github.com/meilisearch/meilisearch/pull/6273) - Bump tar from 0.4.44 to 0.4.45 in [#&#8203;6271](https://github.com/meilisearch/meilisearch/pull/6271) - Bump actix-web-lab from 0.24.3 to 0.26.0 in [#&#8203;6218](https://github.com/meilisearch/meilisearch/pull/6218) - Bump quinn-proto from 0.11.13 to 0.11.14 in [#&#8203;6217](https://github.com/meilisearch/meilisearch/pull/6217) ##### 🪲 Bug fixes - Check char boundaries when hiding secrets by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6262](https://github.com/meilisearch/meilisearch/pull/6262) - Network fixes by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6255](https://github.com/meilisearch/meilisearch/pull/6255) - Override "default" source base url with the config one to support AWS bedrock OpenAI API by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5905](https://github.com/meilisearch/meilisearch/pull/5905) - Fix panic on virtiofs filesystem by [@&#8203;itsamine27](https://github.com/itsamine27) in [#&#8203;6261](https://github.com/meilisearch/meilisearch/pull/6261) ##### 🔩 Miscellaneous - Add `X-Accel-Buffering: no` for `/logs/stream` route by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6268](https://github.com/meilisearch/meilisearch/pull/6268) - Add link to documentation on `--experimental-allowed-ip-networks` parameter by [@&#8203;paulden](https://github.com/paulden) in [#&#8203;6263](https://github.com/meilisearch/meilisearch/pull/6263) - Update sysinfo version to `0.38.4` by [@&#8203;GuillaumeGomez](https://github.com/GuillaumeGomez) in [#&#8203;6211](https://github.com/meilisearch/meilisearch/pull/6211) - Add a no-agent [AGENTS.md](http://agents.md/) file to prevent excessive AI-generated PRs by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6256](https://github.com/meilisearch/meilisearch/pull/6256) #### New Contributors - [@&#8203;GuillaumeGomez](https://github.com/GuillaumeGomez) made their first contribution in [#&#8203;6211](https://github.com/meilisearch/meilisearch/pull/6211) - [@&#8203;itsamine27](https://github.com/itsamine27) made their first contribution in [#&#8203;6261](https://github.com/meilisearch/meilisearch/pull/6261) ### [`v1.39.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.39.0): 🐳​ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.38.2...v1.39.0) ### What's Changed #### **✨ Enhancement** ##### 🔬 Cross-index document hydration Add a new `ForeignKeys` setting allowing to hydrate documents with documents coming from other indexes. > 📓 Note: This implementation doesn't support a remote sharding environment ##### `foreignKeys` experimental feature A new experimental feature, `foreignKeys`, has been added to the `/experimental-feature` route that must be set to true to activate the hydration. ``` curl -X PATCH 'http://127.0.0.1:7700/experimental-features' \ -H 'Content-Type: application/json' \ --data-binary '{"foreignKeys": true}' ``` ##### `foreignKeys` index setting A new index setting, `foreignKeys`, has been added to the `/indexes/{index_uid}/settings`: ```jsonc // new setting, an array of foreign keys that allows multiple foreign relationships between indexes "foreignKeys": [ { // the path in the JSON document containing foreign document ids "fieldName": "actors", // the UID of the foreign index containing the documents to fetch during hydration "foreignIndexUid": "actors" } ] ``` <details> <summary> ##### Example </summary> With this new feature, a document shaped as follows: ```jsonc { "id": 1, "title": "Forrest Gump", // Document IDs in foreign index "actors": [ 1 ] } ``` Will be hydrated as follows in a search response: ```jsonc { "id": 1, "title": "Forrest Gump", "actors": [ { "id": 1, "name": "Tom", "familyName": "Hanks", "birthDate": "1956-07-09" } ] } ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6047](https://github.com/meilisearch/meilisearch/issues/6047) ##### Disable proxy response buffering on Server-Sent Events (SSE) Add `X-Accel-Buffering: no` on `POST /chats/{workspace_uid}/chat/completions` when the streaming mode is activated. By **[@&#8203;YoEight](https://github.com/YoEight)** in [#&#8203;6228](https://github.com/meilisearch/meilisearch/pull/6228) #### 🪲 Bug fixes - Fix a memory leak in the indexation pipeline by **[@&#8203;Kerollmops](https://github.com/Kerollmops)** in [#&#8203;6212](https://github.com/meilisearch/meilisearch/pull/6212) We fixed an important memory leak caused by an invalid use of bumpalo. If you've seen Meilisearch using more and more memory over time, this issue is no longer visible in the latest version. If you want to read more about the bumpalo-trap we felt in, [here is a good summary](https://docs.rs/bumpalo/latest/bumpalo/#deallocation-en-masse-but-no-drop). It looks like this leak was introduced in v1.12, so approximately a year ago... - Avoid losing tasks by applying deltas on the wtxn view by **[@&#8203;Kerollmops](https://github.com/Kerollmops)** in [#&#8203;6222](https://github.com/meilisearch/meilisearch/pull/6222) We addressed a small performance regression introduced in v1.38.1 that affected sending updates to the engine during task deletion. We've restored the task deletion performance to match v1.38.0 levels and ensured no race conditions occur while still allowing updates during deletion. #### **🔩 Miscellaneous** - Ignore flaky test on windows by **[@&#8203;dureuill](https://github.com/dureuill)** in [#&#8203;6226](https://github.com/meilisearch/meilisearch/pull/6226) - Fix small documentation mistakes by **[@&#8203;ManyTheFish](https://github.com/ManyTheFish)** in [#&#8203;6205](https://github.com/meilisearch/meilisearch/pull/6205) - Improve messaging when field is missing in the settings indexing pipeline by **[@&#8203;Kerollmops](https://github.com/Kerollmops)** in [#&#8203;6213](https://github.com/meilisearch/meilisearch/pull/6213) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.38.0...v1.39.0> ### [`v1.38.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.38.2): 🐍 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.38.1...v1.38.2) Meilisearch v1.38.2 fixes a regression introduced in Meilisearch v1.38.0 where Meilisearch could sometimes stop processing tasks after an automatic task queue cleanup performed while more tasks where being added. We recommend that all users in v1.38.0 and v1.38.1 migrate to v1.38.2. Note that the dumpless upgrade process can take up to one minute before the HTTP server becomes available when migrating from a previous v1.38 version. **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.38.1...v1.38.2> ### [`v1.38.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.38.1): 🐍 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.38.0...v1.38.1) Meilisearch v1.38.1 fixes a regression we have seen in task processing, which caused the engine to stop processing tasks. ##### 🪲 Bug fixes - Revert, optimize, and fix task deletion. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6219](https://github.com/meilisearch/meilisearch/pull/6219) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.38.0...v1.38.1> ### [`v1.38.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.38.0): 🐍 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.37.0...v1.38.0) Meilisearch v1.38 drastically improves indexing performance for embeddings, cleans up the task queue of orphan tasks and batches, ensures they are correctly deleted now, fixes issues users may encounter with OpenAI or VoyageAI when generating embeddings, and improves the tooling for generating routes in the documentation. ##### **✨ Enhancement** - Embeddings: Use the latest version of hannoy with improved performances by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6184](https://github.com/meilisearch/meilisearch/pull/6184) We drastically reduced embedding indexing time by eliminating full database scans. It is more efficient to add a couple of embeddings to a large database now. - Tasks: Optimize and fix task deletion by [@&#8203;Mubelotix](https://github.com/Mubelotix) and [@&#8203;kerollmops](https://github.com/kerollmops) in [#&#8203;5828](https://github.com/meilisearch/meilisearch/pull/5828) ##### 🪲 Bug fixes - Embedders: Fix the intermittent `connection reset by peer` errors when embedding documents or search queries using a remote embedder. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6191](https://github.com/meilisearch/meilisearch/pull/6191) ##### 🔩 Miscellaneous - Enforce that routes appear in the reference documentation by [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;manythefish](https://github.com/manythefish) in [#&#8203;6200](https://github.com/meilisearch/meilisearch/pull/6200) [The reference API](https://www.meilisearch.com/docs/reference/api/) is now generated from the source code, but it used to miss some actix-declared routes. It is now mandatory to attach a route when using the newly-provided `routes::routes` and `routes::path` macros, which ensures the route is added to the reference. Please refer to the documentation of the individual macros and the many examples throughout the codebase for more details. - Chore: remove verbose debug log on list documents by [@&#8203;StephaneRob](https://github.com/StephaneRob) in [#&#8203;6198](https://github.com/meilisearch/meilisearch/pull/6198) - Add guide to [CONTRIBUTING.md](http://contributing.md/) to test doc locally by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6180](https://github.com/meilisearch/meilisearch/pull/6180) - Docs: capitalize LangChain and MCP in README by [@&#8203;24f1000637](https://github.com/24f1000637) in [#&#8203;6183](https://github.com/meilisearch/meilisearch/pull/6183) - Docs: improve documentation of the parameters of the search route by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6194](https://github.com/meilisearch/meilisearch/pull/6194) ##### New Contributors - [@&#8203;StephaneRob](https://github.com/StephaneRob) made their first contribution in [#&#8203;6198](https://github.com/meilisearch/meilisearch/pull/6198) - [@&#8203;24f1000637](https://github.com/24f1000637) made their first contribution in [#&#8203;6183](https://github.com/meilisearch/meilisearch/pull/6183) ### [`v1.37.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.37.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.36.0...v1.37.0) > \[!IMPORTANT]\ > This release contains [**breaking changes**](#v137-replicated-sharding-breaking-changes) for users of the `network` experimental feature. Meilisearch v1.37 introduces [replicated sharding](#v137-replicated-sharding), removes the [`vectorStoreSetting` experimental feature](#v137-vector-store), stabilizes our new vector store for best performance, adds a [security fix](#v137-security) and [miscellaneous improvements](#v137-misc). ### ✨ Improvements #### <a id="v137-replicated-sharding" href="#v137-replicated-sharding">§</a> Replicated sharding > \[!NOTE] > Replicated sharding requires Meilisearch Enterprise Edition (EE). > > - Users of Meilisearch Cloud, please contact support if you need replicated sharding. > - Users of the Community Edition, please contact the sales if you want to use replicated sharding in production. ##### <a id="v137-replicated-sharding-breaking-changes" href="#v137-replicated-sharding-breaking-changes">§</a> Breaking changes - `network` objects sent to the `PATCH /network` route must now contain at least one `shard` object containing at least one remote when `leader` is not `null`. Existing databases will be migrated automatically when upgraded with `--experimental-dumpless-upgrade` when `leader` is not `null`, such that for each remote: 1. A shard with the same name as the remote is created 2. This shard has exactly one remote in its `remotes` list: the remote with the same name as the shard. This change will not cause any document to be resharded. To be able to upgrade without resharding, the migration uses the same name for remotes and for shards. However, in new configurations, we recommend using different names for shards and remotes. <details> <summary>Example of migration</summary> For instance, the following network object: ```jsonc { "leader": "ms-00", "self": "ms-01", "remotes": { "ms-00": { /* .. */ }, "ms-01": { /* .. */ } } } ``` is converted to: ```jsonc { "leader": "ms-00", "self": "ms-01", "remotes": { "ms-00": { /* .. */ }, "ms-01": { /* .. */ } }, "shards": { // ✨ NEW "ms-00": { // shard named like the remote "remotes": ["ms-00"] // is owned by the remote }, "ms-01": { "remotes": ["ms-01"] } } } ``` </details> ##### Addition of `network.shards` The `network` object for routes `PATCH /network` and `GET /network` now contains the new field `shards`, which is an object whose values are `shard` objects, and keys the name of each shard. Each `shard` object contains a single field `remotes`, which is an array of strings, each string representing the name of an existing remote. ##### Convenience fields The `shard` objects in `PATCH /network` contain the additional fields `addRemotes` and `removeRemotes` meant for convenience: - pass an array of remote names to `shard.addRemotes` to add these remotes to the list of remotes of a shard. - pass an array of remote names to `shard.removeRemotes` to remove these remotes from the list of remotes of a shard. - if present and non-`null`, `shard.remotes` will completely override the existing list of remotes for a shard. - if several of these options are present and non-`null`, then the order of application is `shard.remotes`, then `shard.addRemotes`, then `shard.removeShards`. <details> <summary>Adding a new shard with some remotes</summary> ```jsonc // PATCH /network { // assuming that remotes `ms-0`, `ms-1`, `ms-2` where sent in a previous call to PATCH /network "shards": { "s-a": { // new shard "remotes": ["ms-0", "ms-1"] } } } ``` Remotes `ms-0` and `ms-1` own the new shard `s-a`. </details> <details> <summary>Fully overriding the list of remotes owning a shard</summary> ```jsonc // PATCH /network { // assuming remotes `ms-0`, `ms-1`, `ms-2` // assuming shard `s-a`, owned by `ms-0` and `ms-1` "shards": { "s-a": { "remotes": ["ms-2"] } } } ``` `ms-2` is now the sole owner of `s-a`, replacing `ms-0` and `ms-1`. </details> <details> <summary>Adding a remote without overriding the list of remotes owning a shard</summary> ```jsonc // PATCH /network { // assuming remotes `ms-0`, `ms-1`, `ms-2` // assuming shard `s-a`, owned by `ms-2` "shards": { "s-a": { "addRemotes": ["ms-0"] } } } ``` `ms-0` and `ms-2` are now the owners of `s-a`. </details> <details> <summary>Removing a remote without overriding the list of remotes owning a shard</summary> ```jsonc // PATCH /network { // assuming remotes `ms-0`, `ms-1`, `ms-2` // assuming shard `s-a`, owned by `ms-0` and `ms-2` "shards": { "s-a": { "removeRemotes": ["ms-2"] } } } ``` `ms-0` is now the sole owner of `s-a`. </details> <details> <summary>Entirely removing a shard from the list of shards</summary> Set the shard to `null`: ```jsonc // PATCH /network { "shards": { "s-a": null } } ``` Or set its `remotes` list to the empty list: ```jsonc // PATCH /network { "shards": { "s-a": { "remotes": [] } } } ``` </details> ##### `network.shards` validity When `network.leader` is not `null`, each `shard` object in `network.shards` must: 1. Only contain `remotes` that exist in the list of `remotes`. 2. Contain at least one remote. Additionally, `network.shards` must contain at least one shard. Failure to meet any of these conditions will cause the `PATCH /network` route to respond with `400 invalid_network_shards`. ##### Change in sharding logic Documents are now sharded according to the list of shards declared in the network rather than the list of remotes. All remotes owning a shard will process the documents that belong to this shard, allowing for replication. <details> <summary>Example of replication</summary> The following configuration defines 3 remotes `0`, `1` and `2`, and 3 shards `A`, `B`, `C`, such that each remote owns two shards, achieving replication (losing one remote does not lose any document). ```jsonc { "leader": "0", "self": "0", "remotes": { "0": { /* .. */ }, "1": { /* .. */ }, "2": { /* .. */ } }, "shards": { "A": { "remotes": ["0", "1"] }, "B": { "remotes": ["1", "2"] }, "C": { "remotes": ["2", "0"] } } } ``` </details> - Full replication is supported by having all remotes own all the shards. - Unbalanced replication is supported by having some remotes own more shards than other remotes. - "Watcher" remotes are supported by having remotes that own no shards. Watcher remotes are not very useful in this release, and might be upgraded in a future release, so that they keep all documents without indexing them, allowing to "respawn" shards for other remotes. ##### `useNetwork` takes `network.shards` into account When `useNetwork: true` is passed to a search query, it is expanded to multiple queries such that each shard declared in `network.shards` appears exactly once, associated with a remote that owns that shard. This ensures that there is no missing or duplicate documents in the results. ##### `_shard` filters When the `network` experimental feature is enabled, then it becomes possible to filter documents depending on the shard they belong to. Given `s-a` and `s-b` the names of two shards declared in `network.shards`, then: - `_shard = "s-a"` in a `filter` parameter to the search or documents fetch will return the documents that belong to `s-a`. - `_shard != "s-a"` will return the documents that do **not** belong to `s-a` - `_shard IN ["s-a", "s-b"]` will return the documents that belong to `s-a` or to `s-b`. You can use these new filters in manual remote federated search to create a partitioning over all shards in the network. > \[!IMPORTANT] > To avoid duplicate or missing documents in results, for manually crafted remote federated search requests, all shards should appear in **exactly one** query. > \[!TIP] > Search requests built with `useNetwork: true` already build a correct partitioning over shards. They should be preferred to manually crafted remote federated search requests in replicated sharding scenarios. ##### Update instructions When updating your Meilisearch network using dumpless upgrade, please observe the following guidelines: 1. Do not call the `PATCH /network` route until all remotes of the network are finished updating 2. If using the search routes with `useNetwork: true`, call them on un-updated remotes. Calling it on already updated remotes will cause un-updated remotes to fail the search as they don't know about the `_shard` filters. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6128](https://github.com/meilisearch/meilisearch/pull/6128) #### <a id="v137-vector-store" href="#v137-vector-store">§</a> Remove `vectorStoreSetting` experimental feature The new HNSW vector store ([hannoy](https://github.com/nnethercott/hannoy)) has been stabilized and is now the only supported vector store in Meilisearch. As a result, updating to v1.37.0 will migrate all remaining legacy vector store indexes (using arroy) to hannoy, and the [`vectorStoreSetting` experimental feature](https://github.com/orgs/meilisearch/discussions/860) is no longer available. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6176](https://github.com/meilisearch/meilisearch/pull/6176) #### Improve indexing performance for embeddings We removed a computationally expensive step from vector indexing. On a DB with 20M documents, this removes 300s per indexing batch of 1100s. By [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6175](https://github.com/meilisearch/meilisearch/pull/6175) #### <a id="v137-security" href="#v137-security">§</a> 🔒 Security - Bump mini-dashboard (local web interface) which - now stores API key in RAM instead of in the `localStorage` - bumps dependencies with potential security vulnerabilities By [@&#8203;Strift](https://github.com/Strift) and [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6186](https://github.com/meilisearch/meilisearch/pull/6186) and [#&#8203;6172](https://github.com/meilisearch/meilisearch/pull/6172) #### <a id="v137-misc" href="#v137-misc">§</a> 🔩 Miscellaneous - Mark Cargo.lock as not linguist-generated by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6181](https://github.com/meilisearch/meilisearch/pull/6181) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.36.0...v1.37.0> ### [`v1.36.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.36.0): 🐙 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.35.1...v1.36.0) Version v1.36.0 introduces an exciting update to the ranking rules to improve the engine's relevance. It's actually the first time we've made such a change since v1.0, and we're really happy about this improvement! ##### ✨ Enhancement - Introduce the `attributeRank` and `wordPosition` criteria by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6154](https://github.com/meilisearch/meilisearch/pull/6154), [#&#8203;6155](https://github.com/meilisearch/meilisearch/pull/6155), and [#&#8203;6164](https://github.com/meilisearch/meilisearch/pull/6164) We released two new ranking rules that Meilisearch had already been using internally for the `attribute` one, which is basically both ranking rules applied one after the other: - `attributeRank`: A document is considered better if the query words match in a higher searchable attribute. It ignores the position of the query words in this attribute. - `wordPosition`: A document is considered better if the query words match closer to the beginning of an attribute. The attribute rank is ignored by this rule. - We continue our policy of migrating everyone to use a homemade HNSW by introducing a new dumpless upgrade step that migrates index uses the old annoy vector store to the new Hannoy one. Changing the vector store backend affects the ranking score. This step can take a couple of minutes when the number of embeddings is high, and we recommend changing the vector store backend beforehand to gain more control if needed. To do so, you must enable the `vectorStoreSetting` experimental feature and set the `vectorStore` root setting to `experimental`. ##### 🪲 Bug fixes - Fix search failing when using `attributesToSearchOn` on an empty index by [@&#8203;zen-zap](https://github.com/zen-zap) in [#&#8203;5944](https://github.com/meilisearch/meilisearch/pull/5944) ##### 🔒 Security - Bump bytes from 1.11.0 to 1.11.1 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6142](https://github.com/meilisearch/meilisearch/pull/6142) - Bump jsonwebtoken from 9.3.1 to 10.3.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6141](https://github.com/meilisearch/meilisearch/pull/6141) - Bump time from 0.3.44 to 0.3.47 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6144](https://github.com/meilisearch/meilisearch/pull/6144) - Bump rsa from 0.9.9 to 0.9.10 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6149](https://github.com/meilisearch/meilisearch/pull/6149) ##### 🔩 Miscellaneous - Improve OpenAPI docs and CIs to improve documentation experience by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6145](https://github.com/meilisearch/meilisearch/pull/6145) > \[!WARNING] > Breaking change: the `meilisearch-openapi-mintlify.json` file will not be available in the release assets anymore. If you were using it, please refer to the one that is now available [in our public documentation repository](https://github.com/meilisearch/documentation/blob/main/assets/open-api/meilisearch-openapi-mintlify.json). - GenAI contributing and PR template changes by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6140](https://github.com/meilisearch/meilisearch/pull/6140) - Fix "test with almost all features" by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6139](https://github.com/meilisearch/meilisearch/pull/6139) and [#&#8203;6148](https://github.com/meilisearch/meilisearch/pull/6148) - Allow any IP for SDK tests by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6151](https://github.com/meilisearch/meilisearch/pull/6151) - Improve output of the declarative tests, also in [#&#8203;6164](https://github.com/meilisearch/meilisearch/pull/6164) ❤️ Thanks to [@&#8203;zen-zap](https://github.com/zen-zap) for contributing to this release! ### [`v1.35.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.35.1) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.35.0...v1.35.1) ### 🦋 Bug fixes Meilisearch v1.35.1 fixes a possible task database corruption issue that would occur when using the S3 streaming snapshot method. - Users of the Community Edition do not need to upgrade as this feature is Enterprise Edition only - Affected users of the Cloud have been contacted. #### Details While snapshotting the task database, sending a task to Meilisearch could corrupt it. Index DBs were not affected, so manually rebuilding the task database fixes the corruption. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6160](https://github.com/meilisearch/meilisearch/issues/6160) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.35.0...v1.35.1> ### [`v1.35.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.35.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.34.3...v1.35.0) Meilisearch v1.35.0 contains improvements to the observability of the search performance, a breaking change to the recently introduced `POST /indexes/<index_uid>/fields` route, and other bugfixes and improvements. ### 🌈 Improvements #### Observe the search performance The search routes accept a new field named `showPerformanceDetails`. When set to `true`, the search response contains a performance trace, allowing the user to better understand what takes time during a search query. **impacted routes:** - `POST /indexes/<index_uid>/search` - `GET /indexes/<index_uid>/search` - `POST /multi-search` - `POST /indexes/<index_uid>/similar` - `GET /indexes/<index_uid>/similar` ##### Search routes: `POST /indexes/<index_uid>/search` and `GET /indexes/<index_uid>/search` ##### Request new request parameters: - `showPerformanceDetails`: `true`/`false` (boolean) <details> <summary>example</summary> ```jsonc { "q": "glass", "showPerformanceDetails": true } ``` </details> ##### Response new response field: - `performanceDetails`: `{"<span>": "<human_duration>", .. }` (map) <details> <summary>example</summary> ```jsonc { "hits": [ // hits .. ], "query": "glass", "processingTimeMs": 5, "limit": 20, "offset": 0, "estimatedTotalHits": 1, "requestUid": "<uuid>", "performanceDetails": { "wait for permit": "295.29µs", "search > tokenize": "436.67µs", "search > resolve universe": "649.00µs", "search > keyword search": "515.71µs", "search > format": "288.54µs", "search": "3.56ms" } } ``` </details> ##### Multi-search route: `POST /multi-search` ##### Request new request parameters: - `queries.showPerformanceDetails`: `true`/`false` (boolean) <details> <summary>example</summary> ```jsonc "queries": [ { "indexUid": "<index_uid>", "q": "glass", "showPerformanceDetails": true } ] ``` </details> ##### Response new response field: - `results.performanceDetails`: `{"<span>": "<human_duration>", .. }` (map) <details> <summary>example</summary> ```jsonc { "results": [ { "indexUid": "<index_uid>", "hits": [ // hits .. ], "query": "glass", "processingTimeMs": 5, "limit": 20, "offset": 0, "estimatedTotalHits": 1, "requestUid": "<uuid>", "performanceDetails": { "wait for permit": "295.29µs", "search > tokenize": "436.67µs", "search > resolve universe": "649.00µs", "search > keyword search": "515.71µs", "search > format": "288.54µs", "search": "3.56ms" } } ] } ``` </details> ##### Federated Search route: `POST /multi-search` ##### Request new request parameters: - `federation.showPerformanceDetails`: `true`/`false` (boolean) <details> <summary>example</summary> ```jsonc { "federation": { "showPerformanceDetails": true }, "queries": [ { "indexUid": "<index_uid>", "q": "glass" } ] } ``` </details> ##### Response new response field: - `performanceDetails`: `{"<span>": "<human_duration>", .. }` (map) <details> <summary>example</summary> ```jsonc { "hits": [ // hits .. ], "query": "glass", "processingTimeMs": 5, "limit": 20, "offset": 0, "estimatedTotalHits": 1, "requestUid": "<uuid>", "performanceDetails": { "wait for permit": "213.83µs", "search > tokenize": "171.67µs", "search > resolve universe": "257.63µs", "search > keyword search": "577.71µs", "search > format": "114.96µs", "search > federation > wait for remote results": "62.71µs", "search > federation > merge results": "120.04µs", "search > federation > merge facets": "53.42µs", "search > federation": "237.04µs", "search": "289.08ms" } } ``` </details> ##### Similar routes: `POST /indexes/<index_uid>/similar` and `GET /indexes/<index_uid>/similar` ##### Request new request parameters: - `showPerformanceDetails`: `true`/`false` (boolean) <details> <summary>example</summary> ```jsonc { "id": 143, "embedder": "manual", "showPerformanceDetails": true } ``` </details> ##### Response new response field: - `performanceDetails`: `{"<span>": "<human_duration>", .. }` (map) <details> <summary>example</summary> ```jsonc { "hits": [ // hits .. ], "id": "143", "processingTimeMs": "[duration]", "limit": 20, "offset": 0, "estimatedTotalHits": 4, "performanceDetails": { "search > format": "244.92µs", "search": "1.25ms" } } ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6132](https://github.com/meilisearch/meilisearch/pull/6132) #### Stabilize multithreaded post-processing of facets and prefixes Multithreaded post-processing of facets and prefixes speeds-up indexing on multi-core machines. Before v1.35.0, it could be disabled with an [experimental feature](https://github.com/orgs/meilisearch/discussions/862). Meilisearch v1.35.0 removes that experimental feature, resulting in the multithreaded post-processing being always enabled. Cloud users upgrading to v1.35.0 will benefit from the speed-up. By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6130](https://github.com/meilisearch/meilisearch/pull/6130) ### 🦋 Fixes #### Breaking change: return pagination fields in `POST /indexes/<index_uid>/fields` route > \[!WARNING] > **Breaking change**: The `POST /indexes/<index_uid>/fields` route now returns an object containing the `results`, `offset`, `limit`, and `total` fields instead of returning an array of results. This change allows to know how many fields match a given filter <details> <summary>Example: before/after</summary> Before: ```jsonc [ // fields .. ] ``` After: ```jsonc { "results": [ // [fields .. ] ], "offset": 0, "limit": 20, "total": 0 } ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6126](https://github.com/meilisearch/meilisearch/pull/6126) #### `POST /indexes/<index_uid>/fields`: Fix pattern filtering when a parent field was matching a child pattern: `title` was matching the pattern `title.to*`. <details> <summary>Example: before/after</summary> For the following request: ```jsonc { "filter": { "attributePatterns": [ "title.en" ] } } ``` Before Response, `title` field is returned: ```jsonc { "results": [ { "name": "title", //metadata... }, ], "offset": 0, "limit": 20, "total": 1 } ``` After Response, nothing returned: ```jsonc { "results": [], "offset": 0, "limit": 20, "total": 0 } ``` </details> By [@&#8203;ManyTheFish](https://github.com/ManyTheFish), also in [#&#8203;6126](https://github.com/meilisearch/meilisearch/pull/6126) #### 🐛 Other fixes - Bump mini-dashboard version to fix display of image in local UI interface by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6129](https://github.com/meilisearch/meilisearch/pull/6129) - Fix mTLS compatibility with Go by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6133](https://github.com/meilisearch/meilisearch/pull/6133) ### 🔩 Miscellaneous - Add AI usage disclosure guidelines to CONTRIBUTING.md by [@&#8203;meili-bot](https://github.com/meili-bot) in [#&#8203;6114](https://github.com/meilisearch/meilisearch/pull/6114) - Expose SettingsDelta and related types for external crate usage by [@&#8203;MkDev11](https://github.com/MkDev11) in [#&#8203;6119](https://github.com/meilisearch/meilisearch/pull/6119) #### New Contributors - [@&#8203;MkDev11](https://github.com/MkDev11) made their first contribution in [#&#8203;6119](https://github.com/meilisearch/meilisearch/pull/6119) ❤️ **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.34.3...v1.35.0> ### [`v1.34.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.34.3) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.34.2...v1.34.3) #### 🐛 Bug Fixes - Increase the auth store database size to 2 GiB so that we can index more keys by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6134](https://github.com/meilisearch/meilisearch/pull/6134) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.34.2...v1.34.3> ### [`v1.34.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.34.2) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.34.1...v1.34.2) This patch fixes an accidental breaking change in v1.34.1 where Meilisearch would not start with a configuration file if `experimental_allowed_ip_networks` was not defined. - Meilisearch Cloud users do not need to update as they were not affected by this regression - We recommend that OSS users upgrade to v1.34.2 **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.34.1...v1.34.2> ### [`v1.34.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.34.1) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.34.0...v1.34.1) In Meilisearch v1.34.1, we released a security fix that affect web queries initiated by Meilisearch. ### 🔐 Security - Cloud users: no action is needed. We found no evidence of exploitation on Meilisearch Cloud and the Cloud is protected at the infrastructure level. - Open-source users: if you allow untrusted users to configure webhooks, embedders or network of machines, we recommend you update to Meilisearch v1.34.1 In Meilisearch versions v1.8 to v1.34.0, a user with an API key with *write permissions* to the configuration of the Meilisearch instance could set up Meilisearch to send POST or GET requests to domains and IPs local to the private network of the Meilisearch instance, effectively bypassing the firewall. The vulnerability has not yet been assigned a CVE number; it has CVE Request [`1975471`](https://github.com/meilisearch/meilisearch/commit/1975471) for CVE ID. Meilisearch v1.34.1 fixes the vulnerability by forbidding Meilisearch from making any requests to a host resolving to a non-global IP, in the sense of the [IANA IPv4 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml) or the [IANA IPv6 Special-Purpose Address Registry](https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml). If you need this functionality in your Meilisearch instance, you can set private IP networks as allowed with the `--experimental-allowed-ip-networks` parameter after reviewing the security implications. **This is a breaking change**, which is allowed for security reasons. #### Allowing non-global IP networks The `--experimental-allowed-ip-networks` CLI flag and the `MEILI_EXPERIMENTAL_ALLOWED_IP_NETWORKS` environment variable control the behavior of Meilisearch with regards to non-global IP networks, with the CLI flag taking precedence over the environment variable when both are specified. - When missing, the default is to reject all web requests resolving to a non-global IP. - When set to a comma-separated list of CIDR-formatted networks (e.g. `192.168.0.0/16,10.0.0.0`), then web requests to the networks from the list will be permitted. Web requests to the non-global IPs not part of the list will still be rejected. - When set to `any`, all web requests will be permitted regardless of the target IP, similar to the behavior of Meilisearch v1.34.0 and lower. Use this option when you control both the machine and the configuration of the deployed Meilisearch instance. #### Acknowledgments Thanks to Gabriel Rodrigues (aka Texugo), for reporting this vulnerability and for helping us improve the security of Meilisearch. ### [`v1.34.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.34.0) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.33.1...v1.34.0) ### 🌈 Improvements #### Easy search over your network of machines ##### `useNetwork` field in `POST /indexes/{:indexUid}/search` The search query object passed in the body of `POST /indexes/{:indexUid}/search` now accepts an optional boolean `useNetwork`. When present and set to `true`, the search is executed "as-if" it was a remote federated search over all remotes in the network. That is, the following: <details> <summary>Search request</summary> ```jsonc // POST /indexes/movies/search { "q": "Batman dark knight returns 1", "filter": "genres IN [Action, Adventure]", "facets": ["genres"], "useNetwork": true, // ✨ NEW "limit": 5 } ``` </details> Is executed by Meilisearch as if it was the following, assuming a network of 3 Meilisearch instances with names `"0", "1" and "2"`: <details> <summary>Equivalent multi-search request</summary> ```jsonc // POST /multi-search { "federation": { "limit": 5, "facetsByIndex": { "movies": [ "genres" ] }, "merge": {} }, "queries": [ { "indexUid": "movies", "federationOptions": { "remote": "0" }, "q": "Batman dark knight returns 1", "filter": "genres IN [Action, Adventure]" }, { "indexUid": "movies", "federationOptions": { "remote": "1" }, "q": "Batman dark knight returns 1", "filter": "genres IN [Action, Adventure]" }, { "indexUid": "movies", "federationOptions": { "remote": "2" }, "q": "Batman dark knight returns 1", "filter": "genres IN [Action, Adventure]" } ] } ``` </details> Resulting in: <details> <summary>Search Response</summary> ```jsonc { "hits": [ { "id": 123025, "title": "Batman: The Dark Knight Returns, Part 1", "overview": "Batman has not been seen for ten years. A new breed of criminal ravages Gotham City, forcing 55-year-old Bruce Wayne back into the cape and cowl. But, does he still have what it takes to fight crime in a new era?", "genres": [ "Action", "Animation", "Mystery" ], "poster": "https://image.tmdb.org/t/p/w500/kkjTbwV1Xnj8wBL52PjOcXzTbnb.jpg", "release_date": 1345507200, "_federation": { "indexUid": "mieli", "queriesPosition": 2, "weightedRankingScore": 0.9894586894586894, "remote": "2" } }, { "id": 142061, "title": "Batman: The Dark Knight Returns, Part 2", "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city. Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.", "genres": [ "Action", "Animation", "Mystery" ], "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg", "release_date": 1357171200, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.9894558963186414, "remote": "1" } }, { "id": 16234, "title": "Batman Beyond: Return of the Joker", "overview": "The Joker is back with a vengeance, and Gotham's newest Dark Knight needs answers as he stands alone to face Gotham's most infamous Clown Prince of Crime.", "genres": [ "Animation", "Family", "Action", "Science Fiction" ], "poster": "https://image.tmdb.org/t/p/w500/7RlBs0An83fqAuKfwH5gKMcqgMc.jpg", "release_date": 976579200, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.9427964918160996, "remote": "1" } }, { "id": 155, "title": "The Dark Knight", "overview": "Batman raises the stakes in his war on crime. With the help of Lt. Jim Gordon and District Attorney Harvey Dent, Batman sets out to dismantle the remaining criminal organizations that plague the streets. The partnership proves to be effective, but they soon find themselves prey to a reign of chaos unleashed by a rising criminal mastermind known to the terrified citizens of Gotham as the Joker.", "genres": [ "Drama", "Action", "Crime", "Thriller" ], "poster": "https://image.tmdb.org/t/p/w500/qJ2tW6WMUDux911r6m7haRef0WH.jpg", "release_date": 1216166400, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.5784178187403994, "remote": "1" } }, { "id": 49026, "title": "The Dark Knight Rises", "overview": "Following the death of District Attorney Harvey Dent, Batman assumes responsibility for Dent's crimes to protect the late attorney's reputation and is subsequently hunted by the Gotham City Police Department. Eight years later, Batman encounters the mysterious Selina Kyle and the villainous Bane, a new terrorist leader who overwhelms Gotham's finest. The Dark Knight resurfaces to protect a city that has branded him an enemy.", "genres": [ "Action", "Crime", "Drama", "Thriller" ], "poster": "https://image.tmdb.org/t/p/w500/vzvKcPQ4o7TjWeGIn0aGC9FeVNu.jpg", "release_date": 1342396800, "_federation": { "indexUid": "mieli", "queriesPosition": 2, "weightedRankingScore": 0.5772657450076805, "remote": "2" } } ], "query": "Batman dark knight returns 1", "processingTimeMs": 173, "limit": 5, "offset": 0, "estimatedTotalHits": 47, "facetDistribution": { "genres": { "Action": 46, "Adventure": 15, "Animation": 34, "Comedy": 3, "Crime": 14, "Drama": 6, "Family": 15, "Fantasy": 8, "Horror": 1, "Mystery": 4, "Romance": 1, "Science Fiction": 14, "TV Movie": 4, "Thriller": 4, "Western": 1 } }, "facetStats": {}, "requestUid": "019bbcf4-a609-7701-8d82-d370611adfb3", "remoteErrors": {} } ``` </details> `useNetwork` requires the `network` experimental feature to be enabled. ##### `useNetwork` query parameter in `GET /indexes/{:indexUid}/search` Passing `useNetwork=true` as a query parameter to `GET /indexes/{:indexUid}/search` has the same effect as passing `useNetwork: true` as a field parameter to `POST /indexes/{:indexUid}/search` ##### `.queries[].useNetwork` field in `POST /multi-search` - `useNetwork` can also be passed as a field of the individual queries inside of a `multi-search` request. - When used on a query in a non-federated search request, it has the same effect as on `POST /indexes/{:indexUid}/search` for that query - When used on a query in a federated search request, the request is executed "as-if" one query per remote of the network had been performed. Federated search example: <details> <summary>Multi-search request</summary> ```jsonc { "federation": { "limit": 5 }, "queries": [ { "q": "Batman returns", "indexUid": "mieli", "useNetwork": true }, { "q": "Superman returns", "indexUid": "mieli", "useNetwork": true } ] } ``` </details> <details> <summary>Multi-search response</summary> ```json { "hits": [ { "id": 364, "title": "Batman Returns", "overview": "While Batman deals with a deformed man calling himself the Penguin, an employee of a corrupt businessman transforms into the Catwoman.", "genres": [ "Action", "Fantasy" ], "poster": "https://image.tmdb.org/t/p/w500/jKBjeXM7iBBV9UkUcOXx3m7FSHY.jpg", "release_date": 708912000, "_federation": { "indexUid": "mieli", "queriesPosition": 0, "weightedRankingScore": 1.0, "remote": "1" } }, { "id": 1452, "title": "Superman Returns", "overview": "Superman returns to discover his 5-year absence has allowed Lex Luthor to walk free, and that those he was closest to felt abandoned and have moved on. Luthor plots his ultimate revenge that could see millions killed and change the face of the planet forever, as well as ridding himself of the Man of Steel.", "genres": [ "Science Fiction", "Action", "Adventure" ], "poster": "https://image.tmdb.org/t/p/w500/qIegbn6DSUYmggfwxOBNOVS35q.jpg", "release_date": 1151452800, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 1.0, "remote": "0" } }, { "id": 324249, "title": "Requiem for Krypton: Making 'Superman Returns'", "overview": "A detailed behind-the-scenes documentary on the making of Superman Returns.", "genres": [ "Documentary" ], "poster": "https://image.tmdb.org/t/p/w500/eC1XKswKSoyDyJXXZszLTuwUHli.jpg", "release_date": 1164672000, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.9907407407407408, "remote": "1" } }, { "id": 294294, "title": "Saltwater", "overview": "This American Indie drama follows several endearing characters as they wade through life seeking happiness, peace and ultimately, love. Will (Ronnie Kerr, Vampire Boys 2, Shut Up and Kiss Me) leaves the Navy after many years, soon reunites old friends and begins to start his new civilian life. His friend Rich (Bruce L Hart) tries to set him up with ruggedly handsome Josh (Ian Roberts-a former Australian professional rugby player, actor and model-Cedar Boys, Superman Returns, Little Fish). While there is immense chemistry between the two, timing and certain ideals never seem to align. When a shocking tragedy happens the two are paired up to pick up the pieces and sort through the after effects. Saltwater is a story about men of all ages, finding love, losing friends, navigating their way through life and knowing it's the journey rather then the destination that's important.", "genres": [ "Romance", "Drama" ], "poster": "https://image.tmdb.org/t/p/w500/bDnLdYqpH9abHo4ASMPKiInx8dm.jpg", "release_date": 1342310400, "_federation": { "indexUid": "mieli", "queriesPosition": 1, "weightedRankingScore": 0.966931216931217, "remote": "1" } }, { "id": 142061, "title": "Batman: The Dark Knight Returns, Part 2", "overview": "Batman has stopped the reign of terror that The Mutants had cast upon his city. Now an old foe wants a reunion and the government wants The Man of Steel to put a stop to Batman.", "genres": [ "Action", "Animation", "Mystery" ], "poster": "https://image.tmdb.org/t/p/w500/arEZYd6uMOFTILne9Ux0A8qctMe.jpg", "release_date": 1357171200, "_federation": { "indexUid": "mieli", "queriesPosition": 0, "weightedRankingScore": 0.8697089947089947, "remote": "1" } } ], "processingTimeMs": 247, "limit": 5, "offset": 0, "estimatedTotalHits": 97, "requestUid": "019bbd3a-5106-70e0-94fc-f58b2f0c28c8", "remoteErrors": {} } ``` </details> ##### Limitations - Facet search referencing `useNetwork` are not supported - The chat route cannot use `useNetwork` at the moment: doing so is not trivial implementation-wise, because chat route expects to be able to open the index (to fetch chat configs), but federated search only opens the indexes once during a short critical section. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6101](https://github.com/meilisearch/meilisearch/pull/6101) #### Federated search supports `page` and `hitsPerPage` Pass `federation.page` and `federation.hitsPerPage` with the same meaning as in a regular search request to use [exhaustive pagination](https://www.meilisearch.com/docs/reference/api/search#page) in the federated search By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6101](https://github.com/meilisearch/meilisearch/pull/6101) #### Speed up settings changes when removing searchable The settings indexer is more efficient when users are removing searchable attributes from the searchable fields. By [@&#8203;VedantMadane](https://github.com/VedantMadane) in [#&#8203;6109](https://github.com/meilisearch/meilisearch/pull/6109) ### 🔒 Security Solves a low-severity timing attack vulnerability on key comparison by using constant-time comparison By [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6077](https://github.com/meilisearch/meilisearch/pull/6077) ### 🔩 Maintenance #### Remove some unwanted dependencies - Remove openssl from deps by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6117](https://github.com/meilisearch/meilisearch/pull/6117) - Fix geo-types version to avoid multiple rstar deps by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6118](https://github.com/meilisearch/meilisearch/pull/6118) ### New Contributors :heart: Thanks again [@&#8203;VedantMadane](https://github.com/VedantMadane) for the contribution to this release! **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.33.1...v1.34.0> ### [`v1.33.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.33.1): 🐞 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.33.0...v1.33.1) In Meilisearch v1.33.1, we released a security fix that affected the dump import, improvements to vector store relevance in massive databases, and a fix related to ranking scores. ##### 🔐 Security Fix - Cloud users: you don't need to do anything. We found no evidence of exploitation of this vulnerability on Meilisearch Cloud. - Open-source users: if you allow importing dumps from an untrusted source, we recommend you update to v1.33.1 All versions of Meilisearch before v1.33.0 are vulnerable to a path traversal vulnerability involving the dump import functionality. Importing a specially crafted dump could result in giving access to the Meilisearch instance to arbitrary, specifically formatted files, present on the file system of the Meilisearch instance. ##### ✨ Enhancements - We updated the vector store to trigger linear scanning even on bigger databases, leading to improved performance and so better result quality when the search cutoff is reached. This applies in particular when the number of filtered candidates is small relative to the number of documents in the index by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6113](https://github.com/meilisearch/meilisearch/pull/6113). ##### 🐛 Bug Fixes - We fixed a bug where only the first non-blocking buckets were taken for the non-final ranking rules. This improves the quality of search results when the search cutoff triggers, especially when vector search and a sort are involved by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6113](https://github.com/meilisearch/meilisearch/pull/6113). **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.33.0...v1.33.1> ### [`v1.33.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.33.0): 🐞 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.32.2...v1.33.0) ##### ✨ Enhancement - **Add `/fields` route to get all the fields of an index** by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6082](https://github.com/meilisearch/meilisearch/pull/6082) Adds a new POST `/indexes/{indexUid}/fields` endpoint that returns detailed metadata about all fields in an index. This endpoint provides comprehensive information about each field's configuration, including display, search, filtering, and localization settings. - **Implement parallel cleanup of old field IDs** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6100](https://github.com/meilisearch/meilisearch/pull/6100) We reduce the time required to perform the dumpless upgrade for instances before v1.32.0 by multi-threading database fetches. By doing that, we noticed improvements from 2 hours and 50 minutes to a bit less than 7 minutes. - **Bump hannoy to 0.1.4-nested-rtxns** by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6103](https://github.com/meilisearch/meilisearch/pull/6103) We updated our internal vector store to speed up the dumpless upgrade by improving the graph rebuilding and improving the speed and relevance of the search by using the explore factor as a limit to stop document searches rather than the query limit. ##### 🪲 Bug fixes - **Meilisearch can now rescale when the index reaches 2 TB** by [@&#8203;Vipul-045](https://github.com/Vipul-045) in [#&#8203;6095](https://github.com/meilisearch/meilisearch/pull/6095) ##### 🔒 Security - **Upgrade mini-dashboard to benefit security vulnerability fixes** by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6091](https://github.com/meilisearch/meilisearch/pull/6091) ##### 🔩 Miscellaneous - Fix tests by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6090](https://github.com/meilisearch/meilisearch/pull/6090) - Add verbose OpenAPI schema descriptions for documentation by [@&#8203;qdequele](https://github.com/qdequele) in [#&#8203;6071](https://github.com/meilisearch/meilisearch/pull/6071) - Add code samples to the generated openAPI file by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6028](https://github.com/meilisearch/meilisearch/pull/6028) Thank you [@&#8203;Vipul-045](https://github.com/Vipul-045) for your first contribution ❤️ ### [`v1.32.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.32.2): 🐟 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.32.1...v1.32.2) #### 🐛 Bug fixes - Do not panic when doing a dumpless upgrade on empty indexes with configured embeddings by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6102](https://github.com/meilisearch/meilisearch/pull/6102) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.32.1...v1.32.2> ### [`v1.32.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.32.1): 🐟 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.32.0...v1.32.1) #### 🌈 Improvements ##### Skip cleaning up the field-ID-based databases Introduce a `MEILI_EXPERIMENTAL_DISABLE_FID_BASED_DATABASES_CLEANUP` env var to opt out of the field ID-based database cleanup when upgrading a Meilisearch from versions inferior to 1.32.0. > by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6096](https://github.com/meilisearch/meilisearch/pull/6096) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.32.0...v1.32.1> ### [`v1.32.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.32.0): 🐟 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.31.0...v1.32.0) #### 🌈 Improvements ##### Log Search performance trace Introduces comprehensive progress tracking and logging for search operations in Meilisearch. It adds detailed timing information for each step of the search process, enabling better observability and performance analysis. > by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6072](https://github.com/meilisearch/meilisearch/pull/6072) ##### Extract document operations from payloads in parallel We accelerate document indexing by processing a large number of tasks in batches or a large number of records in parallel. We expedited the preparation of the payloads by extracting the various changes and assigning internal IDs in parallel. We achieved a 7x speedup on a four-million-document insertion using four CPUs, and the performance scales with the number of CPUs. The `indexedDocuments` field in tasks using skipCreation no longer precisely reflects the number of document operations performed, specifically for `POST` and `PUT` operations. This count may be higher than the actual number of operations, but it doesn't affect the computation; only the reported count is impacted. We prioritize speed over perfect accuracy here, and the documents are still correctly indexed as before. > by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6080](https://github.com/meilisearch/meilisearch/pull/6080) #### 🐛 Bug fixes ##### Vector sort: Bucket documents with same similarity Fixed vector sort bucketing so documents with identical similarity scores are grouped together, ensuring subsequent ranking rules are applied correctly. > by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6081](https://github.com/meilisearch/meilisearch/pull/6081) ##### Properly Delete Documents from FID-Based Databases Fixes a bug where changing searchableAttributes from \["\*"] to a subset of fields left orphaned data in fid-based databases, causing corruption and warnings during search. > by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6076](https://github.com/meilisearch/meilisearch/pull/6076) ##### Rebuild the graph links when dumpless-upgrading Bumps [hannoy to v0.1.3-nested-rtxns](https://github.com/nnethercott/hannoy/releases/tag/v0.1.3-nested-rtxns), which fixes graph-related recall issues and adds a method to rebuild graph links to recover previously malformed graphs. Also fixes a minor issue in the dumpless upgrade flow where the upgrade description was not displayed correctly and related operations were not properly associated with the upgrade. > by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6055](https://github.com/meilisearch/meilisearch/pull/6055) #### 🛠️ Maintenance and Misc. ##### Update JS SDKs tests to use `pnpm` instead of `yarn` Updated the JavaScript SDK tests to use pnpm instead of yarn in CI workflows, switching the package manager across test configurations to ensure the SDK test suite runs correctly and consistently with the current tooling. > by [@&#8203;Strift](https://github.com/Strift) in [#&#8203;6075](https://github.com/meilisearch/meilisearch/pull/6075) ##### Adapt JS tests in SDK tests CI Updated the SDK tests CI workflow for the JavaScript SDKs > by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6050](https://github.com/meilisearch/meilisearch/pull/6050) ##### Bump lru from 0.16.2 to 0.16.3 Fix Stacked Borrows violation in `IterMut`. > by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;6087](https://github.com/meilisearch/meilisearch/pull/6087) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.31.0...v1.32.0> ### [`v1.31.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.31.0): 🦃 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.30.1...v1.31.0) ### 🌈 Improvements #### 🗄️ \[Enterprise Edition] Make the S3-streaming snapshots an Enterprise Edition feature The recently introduced S3-streaming snapshots feature is now available as an Enterprise Edition feature. From now on, you'll need a license to use this feature when using Meilisearch as a self-hosted solution. Note that this version introduces a breaking change regarding the S3-streaming snapshot feature, which is no longer available in the Community Edition; however, on-disk snapshots remain accessible. You can read our BUSL license for contact information, if you like. Note that if you are using the Community Edition of Meilisearch between [version 1.25](https://github.com/meilisearch/meilisearch/releases/tag/v1.25.0) and this release, you can freely use the S3 Streaming feature without an Enterprise Edition license. > by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6057](https://github.com/meilisearch/meilisearch/pull/6057) #### 🔏 \[Enterprise Edition] Support AWS IRSA to authenticate to S3 for snapshotting We just introduced support for IRSA authentication to do snapshots on AWS. IRSA allows the use of short-lived access and secret keys to upload snapshots through S3. This feature is available under the Enterprise Edition and can be accessed through two experimental CLI parameters. > by [@&#8203;paulden](https://github.com/paulden) in [#&#8203;6044](https://github.com/meilisearch/meilisearch/pull/6044) #### ✍️ Allow strict document update without creating missing documents Adds an optional `skipCreation` boolean query parameter to `POST` and `PUT` on `/indexes/{index}/documents`. When set to `true`, documents that don't exist in the index are silently ignored rather than created. Default is `false`, preserving existing behavior. > by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6053](https://github.com/meilisearch/meilisearch/pull/6053) #### 🐛 Bug fixes - Fix actix payload error handling by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6052](https://github.com/meilisearch/meilisearch/pull/6052) - Bump hannoy to v0.1.2 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6063](https://github.com/meilisearch/meilisearch/pull/6063) #### 🛠️ Maintenance and Misc. - Run windows in the PR CI by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6058](https://github.com/meilisearch/meilisearch/pull/6058) - Make CI test titles more human friendly by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6062](https://github.com/meilisearch/meilisearch/pull/6062) ### [`v1.30.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.30.1): 🐸 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.30.0...v1.30.1) ### What's Changed #### 🐛 Bug Fixes ##### Fix task attribution during index swap to prevent cross-index task loss by [@&#8203;YoEight](https://github.com/YoEight) in [#&#8203;6059](https://github.com/meilisearch/meilisearch/pull/6059) This change fixes the parenting of the tasks when doing an index swap. ##### Hotfix: log a warning when FieldidsWeightsMap is missing entry by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6064](https://github.com/meilisearch/meilisearch/pull/6064) This hotfix avoids the encounter of following error during a search request: ```json { "message": "Inside `<query>`: Index `<index_uid>`: internal: missing <field_id> in the fieldids weights mapping.", "code": "internal", "type": "internal", "link": "https://docs.meilisearch.com/errors#internal" } ``` #### 🫂 New Contributors - [@&#8203;YoEight](https://github.com/YoEight) made their first contribution in [#&#8203;6059](https://github.com/meilisearch/meilisearch/pull/6059) ### [`v1.30.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.30.0): 🐸 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.29.0...v1.30.0) ### 🌈 Improvements #### Up and down network scaling Since [v1.19.0](https://github.com/meilisearch/meilisearch/releases/tag/v1.19.0), Meilisearch [Enterprise Edition](https://github.com/meilisearch/meilisearch/blob/main/README.md#-enterprise-edition-ee) allows the automatic sharding of documents over multiple Meilisearch instances, enabling scaling to more documents than a single instance would accommodate. Meilisearch v1.30.0 adds the ability to modify the number of participants in sharding, without having to start over sending documents to a new cluster containing the number of desired machines. To make this possible, Meilisearch v1.30.0 introduces *breaking changes*. These breaking changes only affect the users of the experimental `network` feature who enabled automatic sharding (`network.sharding = true`). Users of the stable features are not affected. ##### Usage <details> <summary>Setting up the initial network</summary> 1. Pick a leader machine that will receive all tasks. Calling a route that creates a dcument, settings or network-related task on a machine that is not the leader will now return an error. 2. Send your network topology to the leader by calling `PATCH /network`: ```jsonc // PATCH /network { "self": "ms0", "leader": "ms0", // must be equal to `self` "remotes": { "ms0": { "url": "URL_OF_MS0", "searchApiKey": "SEARCH_API_KEY_OF_MS0", "writeApiKey": "WRITE_API_KEY_OF_MS0", }, "ms1": { "url": "URL_OF_MS1", "searchApiKey": "SEARCH_API_KEY_OF_MS1", "writeApiKey": "WRITE_API_KEY_OF_MS1", } } } ``` 3. The network is automatically propagated to other members of the network. 4. Send settings and documents as usual, but exclusively to the leader. They will be propagated to all participants in the network, and each participant will process a piece of the documents. </details> <details> <details> <summary>Upgrading from v1.29 or earlier</summary> 1. We recommend using the experimental dumpless upgrade feature to go from Meilisearch v1.13+ to Meilisearch v1.29. 2. When using the experimental dumpless upgrade and the Meilisearch instance already has a `network` instance with `sharding` set to `true`, then the `network` object will be modified so that the leader is the first remote in alphabetic order. For instance, if you network contains remotes: `A`, `B`, `C`, the leader will be set to `A`. </details> <summary>Adding a new remote</summary> 1. Call `PATCH /network` on the leader with the information about the new remote: ```jsonc { "remotes": { // add information about the new remote "ms2": { "url": "URL_OF_MS2", "searchApiKey": "SEARCH_API_KEY_OF_MS2", "writeApiKey": "WRITE_API_KEY_OF_MS2", } // information about existing remotes does not need to be repeated } ``` 4. The new network will be propagated from the leader to all remotes (including the new remote `ms2`). 5. All remotes will register a new `networkTopologyChange` task that will "rebalance" the documents between the existing remotes and the new remote, that is, `ms0` and `ms1` will send parts of their documents to `ms2` </details> <details> <summary>Removing a remote</summary> 1. Call `PATCH /network` on the leader by setting any removed remote to `null`: ```jsonc { "remotes": { // set removed remote to null "ms2": null // information about existing remotes does not need to be repeated } ``` 2. The new network will be propagated from the leader to all remotes (including to the old remote `ms2` that will then no longer participate in the network). 3. All remotes will register a new `networkTopologyChange` task that will "rebalance" the documents between the remaining remotes, that is, `ms2` will send its documents between `ms0` and `ms1` </details> ##### List of changes <details> <summary>List of changes, some of which are breaking</summary> 1. Breaking change: The `Network` object returned or edited by the `/network` route is modified in the following way: - the `sharding` boolean is removed - a `leader` field is added as an optional string. When it is not `null`, it has the same effect (and more) than having `sharding: true` in the previous iteration of the `Network` object. The leader is used as a check when receiving task creation requests. - a `version` field is added as a UUID, defaulting to the null UUID. The version is used when processing tasks. 2. Breaking change: When a `network.leader` is set, calling one of the following routes will fail with `not_a_leader` error if the target's `network.self` is not the same as its `network.leader`: - `POST /indexes` - `PATCH/DELETE /indexes/{:indexUid}` - `POST/PUT/DELETE /indexes/{:indexUid}/documents` - `POST /indexes/{:indexUid}/documents/delete` - `POST /indexes/{:indexUid}/documents/delete-batch` - `POST /indexes/{:indexUid}/documents/edit` - `PATCH/DELETE /indexes/{:indexUid}/settings` and settings sub-routes - `PATCH /network` if the target is the **new** leader - `POST /swap-indexes` 3. Breaking change: when a `leader` is set, `PATCH /network` no longer returns a `Network` object. Rather, it spawns a new `NetworkTopologyChange` task, and returns the summarized task view. 4. Breaking change: Tasks are duplicated by the leader to the entire network when calling the following routes: - `POST /indexes` (new to this PR) - `PATCH/DELETE /indexes/{:indexUid}` (new to this PR) - `POST/PUT/DELETE /indexes/{:indexUid}/documents` (was already the case before this PR) - `POST /indexes/{:indexUid}/documents/delete` (was already the case before this PR) - `POST /indexes/{:indexUid}/documents/delete-batch` (was already the case before this PR) - `POST /indexes/{:indexUid}/documents/edit` (was already the case before this PR) - `PATCH/DELETE /indexes/{:indexUid}/settings` and settings sub-routes (new to this PR) - `PATCH /network` if the target is the **new** leader (new to this PR) - `POST /swap-indexes` (new to this PR) 5. New `NetworkTopologyChange` tasks that perform the following: 1. Execute any remaining task to process with a `network.version` lower than the network task's version 2. Iterate over all documents in all indexes, determine their new shard, and send the document to the remote that must now have it in the new version , deleting it from the local DB - The export route code has been factored and specialized to allow this - Should the export to a remote fail, the corresponding documents are kept locally - If there are no documents to send for an index, still call the documents addition with an empty payload and appropriate headers containing the expected metadata - If there are no documents to send for an entire remote, call the `network` route with specific headers containing the expected metadata 3. Wait for and process tasks from the remotes of the previous version of the network. 6. Breaking change: When importing dumps, we drop the `self` and `leader` from the network 7. Network topology change tasks can be cancelled. In this case the state will be the current one (any moved documents will stay that way). Cancellation needs to happen on all machines. </details> by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6000](https://github.com/meilisearch/meilisearch/pull/6000) #### 🛠️ Maintenance - Fix macos-amd64 compilation by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6037](https://github.com/meilisearch/meilisearch/pull/6037) - Move to Rust v1.91.1 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6039](https://github.com/meilisearch/meilisearch/pull/6039) - Remove risk of command injection in CI by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6041](https://github.com/meilisearch/meilisearch/pull/6041) #### Asset availability note 🌈 The Meilisearch binary is available again for `meilisearch-enterprise-macos-amd64` and `meilisearch-macos-amd64`. It was not available for Meilisearch v1.29. **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.29.0...v1.30.0> ### [`v1.29.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.29.0): 🐑 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.28.2...v1.29.0) #### Build compatibility note The git binary must now be present at build time to populate the `commitSha1` field of the `/version` field. This change was made for build performance reasons. by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6030](https://github.com/meilisearch/meilisearch/pull/6030) #### 🌈 Improvements ##### Another piece of the settings indexer is available: searchable and exact attributes The new settings indexer scales better, supports near-instant cancellations and displays the progress of the indexing operation. Previously, the new settings indexer was enabled only if the **only** changes in a settings batch were to embedder settings. In Meilisearch v1.29.0, the new settings indexer will be enabled if the change is any combination of: - `searchableAttributes` - `exactAttributes` - `proximityPrecision` - `embedders` (as before) Any other change to settings appearing in a batch will cause the batch to use the legacy settings indexer. Additionally, the new settings indexer is currently disabled by default for Cloud users. OSS users who would like to disable the new settings indexer should pass the `MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS` environment variable to `true`. by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5983](https://github.com/meilisearch/meilisearch/pull/5983) ##### Enable the new vector store by default for new indexes [Meilisearch v1.21.0](https://github.com/meilisearch/meilisearch/releases/tag/v1.21.0) introduced a new vector store backend providing better performance and relevancy. Starting with v1.29.0, any newly created index will default to the new backend. Existing indexes will be left unchanged. It is still possible to explicitly choose the vector store backend, please refer to [the relevant experimental feature discussion page](https://github.com/orgs/meilisearch/discussions/860). by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6004](https://github.com/meilisearch/meilisearch/pull/6004) ##### Support more models for `huggingFace` embedder You can now select models with the XLM Roberta architecture when generating embeddings locally on CPU or GPU with the `huggingFace` embedder. by [@&#8203;qdequele](https://github.com/qdequele) in [#&#8203;6018](https://github.com/meilisearch/meilisearch/pull/6018) #### 🦋 Bug fixes - Fix rare internal error in the experimental vector store by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6032](https://github.com/meilisearch/meilisearch/pull/6032) #### 🔧 Maintenance and Misc. Last week was a Quality of Life week, and while we still had improvements in the pipe, the bulk of our work was dedicated to maintenance tasks. Most notably, the CI is now faster, going from over one hour to less than 30 minutes, and also more reliable as it automatically tests the dumpless upgrade. - New workload to run declarative tests. This is, in particular, very useful to automatically test the dumpless upgrade. By [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5861](https://github.com/meilisearch/meilisearch/pull/5861) - The code that applies the dumpless upgrade migrations was rewritten to make it easier to maintain. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6029](https://github.com/meilisearch/meilisearch/pull/6029) - We no longer run macOS and Windows tests at PR time. These CI jobs were very slow and given their limited impact they will only be run on the nightly builds. Ny [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6021](https://github.com/meilisearch/meilisearch/pull/6021) - Send notifications for Kubernetes integration when releasing by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6023](https://github.com/meilisearch/meilisearch/pull/6023) - Introduce `xtask` sub-command to generate prototype tag names with the expected nomenclature by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6022](https://github.com/meilisearch/meilisearch/pull/6022) - Fix misc. CI issues by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;6026](https://github.com/meilisearch/meilisearch/pull/6026) #### Asset availability note ⚠️ The Meilisearch binary is not available for `meilisearch-enterprise-macos-amd64` and `meilisearch-macos-amd64` due to [a compilation oversight](https://github.com/meilisearch/meilisearch/actions/runs/20023402416/job/57415170954). [#&#8203;6037](https://github.com/meilisearch/meilisearch/pull/6037) aims at fixing this for future releases. The more recent `meilisearch-enterprise-macos-apple-silicon` and `meilisearch-macos-apple-silicon` are fine. **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.28.2...v1.29.0> ### [`v1.28.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.28.2): 🐩 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.28.1...v1.28.2) This release fixes a bug affecting the Prometheus metrics route in versions 1.28.0 and 1.28.1, specifically when the instance has too many tasks. The issue is visible as high memory usage and could cause the instance to be OOM-killed. If you are using the /metrics route, we recommend deleting all succeeded or failed tasks in the index using [the dedicated route](https://www.meilisearch.com/docs/reference/api/tasks#query-parameters-3) or upgrading to at least v1.28.2. ##### 🐛 Bug fixes - Limit the number of retrieved tasks to one in the metrics by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6024](https://github.com/meilisearch/meilisearch/pull/6024) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.28.1...v1.28.2> ### [`v1.28.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.28.1): 🐩 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.28.0...v1.28.1) This release features two fixes: one to ensure that we correctly upload the Linux-amd64 binaries for the Community and Enterprise editions, and one contributed by an external developer to ensure that we still return documents that don't contain the sortable attribute after those that do. ##### 🐛 Bug Fixes - Fix sort on /documents endpoint when field has no values by [@&#8203;EclipseAditya](https://github.com/EclipseAditya) in [#&#8203;6016](https://github.com/meilisearch/meilisearch/pull/6016) - Fix release CI after we introduced the enterprise edition by [@&#8203;paulden](https://github.com/paulden) in [#&#8203;6020](https://github.com/meilisearch/meilisearch/pull/6020) ##### 🫂 New Contributors - [@&#8203;EclipseAditya](https://github.com/EclipseAditya) made their first contribution in [#&#8203;6016](https://github.com/meilisearch/meilisearch/pull/6016) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.28.0...v1.28.1> ### [`v1.28.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.28.0): 🐩 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.27.0...v1.28.0) This release introduces improvements to language support and separates the community and enterprise binary editions. We now offer binaries [under the BUSL-1.1 license](https://github.com/meilisearch/meilisearch/blob/main/LICENSE-EE), identified by the "enterprise" term in their names, in addition to our MIT-licensed binaries, which retain their original names. Docker images for the enterprise edition are available in the [`getmeili/meilisearch-enterprise`](https://hub.docker.com/r/getmeili/meilisearch-enterprise/tags) repository. ##### 📝 Licensing - Separation of EE and CE. CE remains the default binary, and the name does not change by Louis on [#&#8203;6011](https://github.com/meilisearch/meilisearch/issues/6011) ##### **✨ Enhancement** - Charabia v0.9.9: introduce a better word segmentation for Thai, Khmer, and German languages by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;6007](https://github.com/meilisearch/meilisearch/issues/6007) - Expose batch progress traces on the metrics route to improve the indexing debugging experience by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5956](https://github.com/meilisearch/meilisearch/issues/5956) ##### **🔩 Miscellaneous** - Remove version from the name of the test job in CI by [@&#8203;paulden](https://github.com/paulden) in [#&#8203;6012](https://github.com/meilisearch/meilisearch/issues/6012) - Upgrade most of the dependencies by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6002](https://github.com/meilisearch/meilisearch/issues/6002) - Build x86 and ARM images on GitHub-hosted runners by [@&#8203;paulden](https://github.com/paulden) in [#&#8203;6003](https://github.com/meilisearch/meilisearch/issues/6003) - Fix SDKs tests to use the enterprise edition and continue testing the sharding feature by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;6013](https://github.com/meilisearch/meilisearch/issues/6013) ##### 🫂 New Contributors - [@&#8203;paulden](https://github.com/paulden) made their first contribution in [#&#8203;6003](https://github.com/meilisearch/meilisearch/issues/6003) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.27.0...v1.28.0> ### [`v1.27.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.27.0): 🦮 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.26.0...v1.27.0) This release improves the batch size for better performance. It also fixes bugs with the embedders that could skip some documents during generation and resolves an issue with the document route that displayed the same documents on multiple pages. It improves the quality of error messages when uploading snapshots to S3, which helps with debugging. ##### ⚙️ Compatibility support - Update macOS platform version in the CI by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;6001](https://github.com/meilisearch/meilisearch/pull/6001) Meilisearch MacOS binaries now generated with MacOS Sonoma (`macos-14`) ##### ✨ Enhancement - Show errors in the task queue to improve debugging of S3 snapshot uploads by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5994](https://github.com/meilisearch/meilisearch/pull/5994) - Batched tasks total size now defaults to half of the max indexing memory to improve task ingestion by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5990](https://github.com/meilisearch/meilisearch/pull/5990) & [#&#8203;6005](https://github.com/meilisearch/meilisearch/pull/6005) ##### 🪲 Bug fixes - Fix issue that could cause Meilisearch to skip some documents when performing embedding operations by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5995](https://github.com/meilisearch/meilisearch/pull/5995) - Every `available_parallelism`th document in a batch was ignored for the purpose of embedding when using a Hugging Face embedder [#&#8203;5976](https://github.com/meilisearch/meilisearch/issues/5976) - Every 40th document in a batch was ignored for the purpose of embedding when using a REST embedder **with only one embedding per request** - To verify if documents in your database have been affected: 1. enable the `multimodal` exp. feature 2. search or fetch with filter: `NOT _vectors EXISTS` to find documents without vectors. - Fix `/documents/fetch` bug that could cause duplicated search results when paginating sorted documents by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5999](https://github.com/meilisearch/meilisearch/pull/5999) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.26.0...v1.27.0> ### [`v1.26.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.26.0): 🐛 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.25.0...v1.26.0) ### ✨ Enhancements #### Allow to attach custom metadata in the document addition or update tasks - To make it easier to keep track of which documents were processed by Meilisearch, it is now possible to attach an arbitrary string to all routes that create document-related tasks. - Tasks created with this custom metadata will display the passed metadata when accessed by the tasks route or sent in webhooks. - To use this feature, add the `customMetadata` query parameter to any supported route: ``` POST /indexes/{indexUid}/documents?customMetadata=my-metadata-for-the-task ``` - Note that, as usual for query parameters, the value of the parameter must be URL-encoded. - List of supported routes: ``` POST /indexes/{indexUid}/documents PUT /indexes/{indexUid}/documents DELETE /indexes/{indexUid}/documents/{documentId} POST /indexes/{indexUid}/documents/delete-batch POST /indexes/{indexUid}/documents/delete POST /indexes/{indexUid}/documents/edit DELETE /indexes/{indexUid}/documents ``` - Sample output of `GET /tasks` for tasks with metadata: ```json { "results": [ { "uid": 37, "batchUid": 37, "indexUid": "mieli", "status": "succeeded", "type": "documentDeletion", "canceledBy": null, "details": { "deletedDocuments": 31944 }, "error": null, "duration": "PT0.511099S", "enqueuedAt": "2025-11-06T16:33:37.816237Z", "startedAt": "2025-11-06T16:33:37.821591Z", "finishedAt": "2025-11-06T16:33:38.33269Z", "customMetadata": "removeall" }, { "uid": 36, "batchUid": 36, "indexUid": "movies", "status": "succeeded", "type": "documentAdditionOrUpdate", "canceledBy": null, "details": { "receivedDocuments": 31968, "indexedDocuments": 31944 }, "error": null, "duration": "PT3.192271S", "enqueuedAt": "2025-10-30T10:31:12.896073Z", "startedAt": "2025-10-30T10:31:12.911905Z", "finishedAt": "2025-10-30T10:31:16.104176Z", "customMetadata": "foo" } ], "total": 38, "limit": 2, "from": 36, "next": 35 } ``` by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5963](https://github.com/meilisearch/meilisearch/pull/5963) #### Support more models for `huggingFace` embedder You can now select models with the `modernBERT` architecture when generating embeddings locally on CPU or GPU with the `huggingFace` embedder. This unlocks for instance [Ruri v3](https://huggingface.co/cl-nagoya/ruri-v3-30m) and [other models](https://huggingface.co/models?other=modernbert) by [@&#8203;hayatosc](https://github.com/hayatosc) in [#&#8203;5980](https://github.com/meilisearch/meilisearch/pull/5980) #### 🧪 Experimental: embedder failure modes You can now decide to ignore some embedder-related errors. Either: 1. Errors related to a document template not rendering properly 2. Errors related to an embedding request to an embedder failing (this includes missing vectors in `userProvided` embedders) 3. Or both kinds of errors. When errors are ignored, the corresponding documents will not have embeddings, but the associated batch of tasks will not be marked as failed. Of course, ignoring errors means that it is harder to notice an issue with embedders, so use this feature parsimoniously. To enable the feature: - Customers of the Cloud, please ask the support. - OSS users, please use the `MEILI_EXPERIMENTAL_CONFIG_EMBEDDER_FAILURE_MODES` and set it to a comma-separated list of errors to ignore, with the possible values: 1. `ignore_document_template_failures` to ignore document template failures 2. `ignore_embedder_failures` to ignore embedder failures - For example: `ignore_document_template_failures,ignore_embedder_failures` ignores both kinds of failures by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5984](https://github.com/meilisearch/meilisearch/pull/5984) #### 🧪 Experimental: timeout control for REST embedders You can now control the duration before a REST embedder request times out. - Customers of the Cloud, please ask the support. - OSS users, please use the `MEILI_EXPERIMENTAL_REST_EMBEDDER_TIMEOUT_SECONDS`, which must be a positive integer. by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5984](https://github.com/meilisearch/meilisearch/pull/5984) ### 🔩 Misc - Remove unused dependency `allocator-api2` by [@&#8203;xuhongxu96](https://github.com/xuhongxu96) in [#&#8203;5969](https://github.com/meilisearch/meilisearch/pull/5969) ### 👥 Contributors Many thanks to our new contributors [@&#8203;hayatosc](https://github.com/hayatosc) and [@&#8203;xuhongxu96](https://github.com/xuhongxu96) ❤️ ### [`v1.25.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.25.0): 🐈‍⬛ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.24.0...v1.25.0) #### ✨ Enhancement ##### 🔬 \[Experimental]: Search personalization by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5775](https://github.com/meilisearch/meilisearch/issues/5775) Add the ability to dynamically rerank the search results based on Cohere using a personalized prompt. For more information on how to set it up, see the dedicated [experimental feature discussion](https://github.com/orgs/meilisearch/discussions/866). ##### 🔬 \[Experimental]: Upload snapshot tarballs to S3 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5948](https://github.com/meilisearch/meilisearch/issues/5948) Add the ability to upload snapshots directly to S3. It has many advantages, such as being able to stream the entire process and effectively utilizing multipart technology to send chunks of data in parallel. For more information on how to use it, see the dedicated [experimental feature discussion](https://github.com/orgs/meilisearch/discussions/869). #### 🪲 Bug fixes ##### ⚠️ \[Breaking - Security] Redact Authorization header in webhooks by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5968](https://github.com/meilisearch/meilisearch/issues/5968) The value of the `Authorization` header is now redacted when getting webhook, getting webhooks, or in the object returned when posting a new webhook or deleting a webhook. - Impact on Cloud: Similarly to embedder API, the UI should make sure to never send the `Authorization` header back after it has been redacted - Technically a **breaking change**, as users could previously get the key value back when getting the webhook, and that will no longer be possible ##### 🚰 Fix the LMDB fork memory leak by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5967](https://github.com/meilisearch/meilisearch/issues/5967) This bug was causing crashes in the recent indexer optimizations. If you deactivated these optimizations by setting the following environment variables: ``` MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_PREFIX_POST_PROCESSING=true MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_FACET_POST_PROCESSING=true ``` You can now safely reactivate them without experiencing memory leaks. ##### 🇩🇪 Hotfix German word segmentation by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [meilisearch/charabia#360](https://github.com/meilisearch/charabia/pull/360) German word segmentation relies on a word dictionary to segment words, but if a word is not part of the dictionary, it is cut into bigrams. The segmenter will now skip segmenting unknown words: ```yaml Source: "Feuchteschutz" Before: ["Fe" "uc" "ht" "es, "ch", "utz"] After: ["Feuchteschutz"] Source: "insgesamt" Before: ["in" "sg" "es" "amt"] After: ["insgesamt"] ``` > If you have a Meilisearch database containing German words, you must reindex your data manually. ##### 🇨🇳 Prevent splitting of numbers and English words in Chinese text segmentation by [@&#8203;JinheLin](https://github.com/JinheLin) in [meilisearch/charabia#354](https://github.com/meilisearch/charabia/pull/354) It’s very common for Chinese, numbers, and English to appear together in the same sentence. We now ensure that numbers and English are not segmented differently between segmenters: ```yaml Source: "我从2025年开始学习Rust语言。" Before: ["我", "从", "2", "0", "2", "5", "年", "开始", "学习", "R", "u", "s", "t", "语言", "。"] After: ["我", "从", "2025", "年", "开始", "学习", "Rust", "语言", "。"] ``` > If you have a Meilisearch database containing Chinese words, you must reindex your data manually. #### 🔩 Miscellaneous - Add Flickr example to README by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5961](https://github.com/meilisearch/meilisearch/pull/5961) Thanks to [@&#8203;JinheLin](https://github.com/JinheLin), [@&#8203;dureuill](https://github.com/dureuill), [@&#8203;Kerollmops](https://github.com/Kerollmops), and [@&#8203;ManyTheFish](https://github.com/ManyTheFish) for their contribution! 🎉 ### [`v1.24.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.24.0): 🦞 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.23.0...v1.24.0) This release features some improvements with the interaction of the vector store and the `searchCutoffMs` when using the `"vectorStore": "experimental"` index setting. It also introduces the metadata header `Meili-Include-Metadata` on the search request that adds a metadata field to the response. These metadatas contains one uid by query and a reminder of the `indexUid` and its primary key. We also introduced minor bug fixes around the compaction to improve the interaction with task cancellation. ##### ✨ Enhancement - Improve the vector store search cutoff by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5945](https://github.com/meilisearch/meilisearch/pull/5945) - Improve compaction behaviors by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5946](https://github.com/meilisearch/meilisearch/pull/5946) - Search metadata by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5926](https://github.com/meilisearch/meilisearch/pull/5926) ##### 🔩 Miscellaneous - Adapt the standards of prototypes by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5942](https://github.com/meilisearch/meilisearch/pull/5942) - Bump Dockerfile alpine version to 3.22 by [@&#8203;PedroTroller](https://github.com/PedroTroller) in [#&#8203;5866](https://github.com/meilisearch/meilisearch/pull/5866) ##### 👥 New Contributors - [@&#8203;PedroTroller](https://github.com/PedroTroller) made their first contribution in [#&#8203;5866](https://github.com/meilisearch/meilisearch/pull/5866) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.23.0...v1.24.0> ### [`v1.23.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.23.0): 🐘 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.22.3...v1.23.0) This release introduces a new compact route on the index routes, which appends a new compaction task to the queue. Meilisearch uses an LMDB environment by index, and indexes start to fragment after some time. We have noticed that the indexes generally have 30% fragmentation. By defragmenting the environment, we've seen large (2-4x) speed-ups in terms of search and indexation. This is primarily due to the reordering of the LMDB internal pages and the removal of scattered free pages throughout the file, thereby relocating the content to the beginning. We also worked on parallelizing the post-processing of facets. We noticed that a lot of time was spent iterating over the prefixes of the index in a single-threaded loop. We redesigned this part of the indexation to make it multi-threaded. We have seen a 4x and 6x improvement in terms of time spent on this operation. #### ✨ Improvements - Introduce a task to compact an index by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5929](https://github.com/meilisearch/meilisearch/pull/5929) - Parallelize bulk facets & word prefix fid/position docids by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5307](https://github.com/meilisearch/meilisearch/pull/5307) - Change Java version in SDK CI by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5910](https://github.com/meilisearch/meilisearch/pull/5910) - Minor improvement in OpenAPI CI by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5834](https://github.com/meilisearch/meilisearch/pull/5834) - Add request uid to search routes by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5863](https://github.com/meilisearch/meilisearch/pull/5863) #### 🦋 Bug Fixes - Fix ranking score bug when sort is present by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5933](https://github.com/meilisearch/meilisearch/pull/5933) - Synonym performance fix by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5930](https://github.com/meilisearch/meilisearch/pull/5930) - Update README.md to fix newsletter link by [@&#8203;EazyAl](https://github.com/EazyAl) in [#&#8203;5911](https://github.com/meilisearch/meilisearch/pull/5911) - Try to fix GH license detection again by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5938](https://github.com/meilisearch/meilisearch/pull/5938) #### 🔩 Miscellenaous - Remove release-drafter and encourage usage of GitHub-generated notes by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5935](https://github.com/meilisearch/meilisearch/pull/5935) - Show Dependabot dependency upgrade in the changelog by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5900](https://github.com/meilisearch/meilisearch/pull/5900) - Bump actions/setup-go from 5 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5912](https://github.com/meilisearch/meilisearch/pull/5912) - Bump actions/setup-dotnet from 4 to 5 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5914](https://github.com/meilisearch/meilisearch/pull/5914) - Bump actions/setup-node from 4 to 5 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5915](https://github.com/meilisearch/meilisearch/pull/5915) - Bump sigstore/cosign-installer from 3.9.2 to 3.10.0 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5916](https://github.com/meilisearch/meilisearch/pull/5916) - Bump actions/setup-python from 5 to 6 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5913](https://github.com/meilisearch/meilisearch/pull/5913) #### New Contributors - [@&#8203;EazyAl](https://github.com/EazyAl) made their first contribution in [#&#8203;5911](https://github.com/meilisearch/meilisearch/pull/5911) **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.22.1...v1.23.0> ### [`v1.22.3`](https://github.com/meilisearch/meilisearch/releases/tag/v1.22.3): 🐦‍🔥 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.22.2...v1.22.3) This version contains a minor fix that affects remote federated search users. If you are not a remote federated search user, it is not necessary to migrate from v1.22.x. ### 🦋 Bugfixes - v1.22.2 raised the remote federated search timeout for waiting nodes from 5 to 30s. This version makes it configurable by setting the environment variable `MEILI_EXPERIMENTAL_REMOTE_SEARCH_TIMEOUT_SECONDS` to a positive integer value. Please note that no CLI flag or configuration entry is available. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5932](https://github.com/meilisearch/meilisearch/pull/5932) ### [`v1.22.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.22.2): 🐦‍🔥 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.22.1...v1.22.2) #### 🦋 Bugfixes - Remote federated search would declare remotes as "timeout'd" after 5s. This timeout was raised to 30s to accomodate some search configurations. By [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5919](https://github.com/meilisearch/meilisearch/pull/5919) ### [`v1.22.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.22.1) [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.22.0...v1.22.1) #### 🐛 Bug Fixes - use the latest version of zerometry that supports collection, lines and multi-lines ([#&#8203;5907](https://github.com/meilisearch/meilisearch/issues/5907)) [@&#8203;irevoire](https://github.com/irevoire) - Delete oldest tasks first ([#&#8203;5906](https://github.com/meilisearch/meilisearch/issues/5906)) [@&#8203;dureuill](https://github.com/dureuill) ❤️ Huge thanks to our contributors: [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;irevoire](https://github.com/irevoire). ### [`v1.22.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.22.0): 🐦‍🔥 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.21.0...v1.22.0) #### :rocket: Enhancements - Introduce a new geo backend to store geojson and filter on polygon 1. Make the `_geojson` field filterable 2. Then send your documents with a `_geojson` field filled with a valid [geojson](https://datatracker.ietf.org/doc/html/rfc7946) 3. Filter your documents with the new `_geoPolygon` filter, or the old `_geoBoudingBox` and `_geoPoints` filter #### :bug: Bug Fixes - Document template: Correctly render when indexing first item in array by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5896](https://github.com/meilisearch/meilisearch/pull/5896) - arroy to hannoy conversion fails with binary quantized distances by [@&#8203;nnethercott](https://github.com/nnethercott) [#&#8203;5891](https://github.com/meilisearch/meilisearch/pull/5891) :heart: Huge thanks to our contributors: [@&#8203;nnethercott](https://github.com/nnethercott), [@&#8203;Kerollmops](https://github.com/Kerollmops), [@&#8203;ManyTheFish](https://github.com/ManyTheFish), [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;irevoire](https://github.com/irevoire). **Full Changelog**: <https://github.com/meilisearch/meilisearch/compare/v1.21.0...v1.22.0> ### [`v1.21.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.21.0): 🐷 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.20.0...v1.21.0) #### 🚀 Enhancements - Introduce a new vector store backend for better performance, especially if using the binary quantization 1. Enable the new `vectorStoreSetting` experimental feature 2. Then change the `vectorSetting` index setting to `"experimental"` for the indexes where you want to try the new vector store - Done in [#&#8203;5767](https://github.com/meilisearch/meilisearch/issues/5767) by [@&#8203;Kerollmops](https://github.com/Kerollmops) - Add Persian support (update charabia to v0.9.7) ([#&#8203;5848](https://github.com/meilisearch/meilisearch/issues/5848)) [@&#8203;ManyTheFish](https://github.com/ManyTheFish) #### 🐛 Bug Fixes - Observing the progress trace during indexing no longer removes parts of the trace ([#&#8203;5884](https://github.com/meilisearch/meilisearch/issues/5884)) [@&#8203;irevoire](https://github.com/irevoire) - Fix dumpless upgrade `decoding error` when upgrading with a `rest` embedder ([#&#8203;5886](https://github.com/meilisearch/meilisearch/issues/5886)) [@&#8203;dureuill](https://github.com/dureuill). - In case you had encountered the issue, use the dumpless upgrade to v1.21 to fix it. ❤️ Huge thanks to our contributors: [@&#8203;ja7ad](https://github.com/ja7ad), [@&#8203;agourlay](https://github.com/agourlay), [@&#8203;Kerollmops](https://github.com/Kerollmops), [@&#8203;ManyTheFish](https://github.com/ManyTheFish), [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;irevoire](https://github.com/irevoire). ### [`v1.20.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.20.0): 🦟 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.19.1...v1.20.0) #### 🚀 Enhancements - Display the progressTrace in in-progress batches ([#&#8203;5858](https://github.com/meilisearch/meilisearch/issues/5858)) [@&#8203;shreeup](https://github.com/shreeup) #### 🐛 Bug Fixes - Send the version when returning prometheus metrics ([#&#8203;5876](https://github.com/meilisearch/meilisearch/issues/5876)) [@&#8203;irevoire](https://github.com/irevoire) #### 🔒 Security - Bump tracing-subscriber from 0.3.19 to 0.3.20 ([#&#8203;5869](https://github.com/meilisearch/meilisearch/issues/5869)) @&#8203;[dependabot\[bot\]](https://github.com/apps/dependabot) #### ⚙️ Maintenance/misc - Fix scheduled CI failure ([#&#8203;5856](https://github.com/meilisearch/meilisearch/issues/5856)) [@&#8203;arithmeticmean](https://github.com/arithmeticmean) ❤️ Huge thanks to our contributors: [@&#8203;ManyTheFish](https://github.com/ManyTheFish), [@&#8203;arithmeticmean](https://github.com/arithmeticmean), [@&#8203;curquiza](https://github.com/curquiza), [@&#8203;dureuill](https://github.com/dureuill), [@&#8203;irevoire](https://github.com/irevoire), [@&#8203;shreeup](https://github.com/shreeup) and [dependabot\[bot\]](https://github.com/apps/dependabot). ### [`v1.19.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.19.1): 🪸 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.19.0...v1.19.1) #### 🐛 Performance improvements ##### Enhance hybrid search with filter performances In previous versions of Meilisearch, mixing hybrid search with filters, as shown below, could multiply the search time by hundreds. ```json { "q": "hello world", "limit": 100, "filter": "tag=science" "hybrid": { "semanticRatio": 0.5, "embedder": "default" } } ``` Meilisearch will now directly compute the semantic distance with the filtered candidates if only a few candidates come from the filter, instead of searching for the closest embeddings matching the filter in the vector database. ### [`v1.19.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.19.0): 🪸 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.18.0...v1.19.0) #### 🚀 Enhancements #### Automatically shard documents to scale horizontally Meilisearch can now automatically distribute documents between multiple instances using the new **sharding** feature. Find a guide on implementing sharding in [the documentation](https://www.meilisearch.com/docs/learn/multi_search/implement_sharding). > \[!NOTE]\ > Sharding is an advanced feature available exclusively in **Meilisearch Enterprise Edition (EE)**. > > The EE features are governed by the [**Business Source License 1.1**](https://github.com/meilisearch/meilisearch/blob/v1.19.0/LICENSE-EE), which allows you to use, test, and develop with sharding for free in non-production environments. Please [reach out to us](mailto:sales@meilisearch.com) before using it in production. Added in [#&#8203;5784](https://github.com/meilisearch/meilisearch/issues/5784) by [@&#8203;dureuill](https://github.com/dureuill) #### 🐛 Bug Fixes - Takes the allowed max memory of the container when computing the max memory to use ([#&#8203;5729](https://github.com/meilisearch/meilisearch/issues/5729)) [@&#8203;martin-g](https://github.com/martin-g) ❤️ Huge thanks to our contributors: [@&#8203;Kerollmops](https://github.com/Kerollmops), [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;martin-g](https://github.com/martin-g). ### [`v1.18.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.18.0): 🕷️ [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.17.1...v1.18.0) #### 🚀 Enhancements - Return `queryVector` in the search response when using `retrieveVectors` ([#&#8203;5778](https://github.com/meilisearch/meilisearch/issues/5778)) [@&#8203;Mubelotix](https://github.com/Mubelotix) - Allow retrieving documents with vectors from specific embedders ([#&#8203;5741](https://github.com/meilisearch/meilisearch/issues/5741)) [@&#8203;Mubelotix](https://github.com/Mubelotix) - Support renaming indexes using the API ([#&#8203;5829](https://github.com/meilisearch/meilisearch/issues/5829)) [@&#8203;irevoire](https://github.com/irevoire) ❤️ Huge thanks to our contributors: [@&#8203;Kerollmops](https://github.com/Kerollmops), [@&#8203;Mubelotix](https://github.com/Mubelotix), [@&#8203;irevoire](https://github.com/irevoire) and [@&#8203;qdequele](https://github.com/qdequele). ### [`v1.17.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.17.1): 🐀 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.17.0...v1.17.1) #### 🚀 Enhancements - Publish OpenAPI file to release assets ([#&#8203;5823](https://github.com/meilisearch/meilisearch/issues/5823)) [@&#8203;curquiza](https://github.com/curquiza) #### ⚙️ Maintenance/misc - Fix update-cargo-version CI ([#&#8203;5831](https://github.com/meilisearch/meilisearch/issues/5831)) [@&#8203;curquiza](https://github.com/curquiza) ### [`v1.17.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.17.0): 🐀 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.16.0...v1.17.0) > \[!NOTE] > Want to make your search feel more natural? Try our new [**chat completions** route](https://www.meilisearch.com/docs/learn/chat/getting_started_with_chat) and turn your queries into conversations. Easy to set up, works with your favorite LLMs. ##### Enhancements - Support Webhook API by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5785](https://github.com/meilisearch/meilisearch/pull/5785) Check the [in progress documentation](https://github.com/meilisearch/documentation/pull/3336/files) (PR merged soon) - Optimize and stabalize performance the `STARTS_WITH` filter by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5783](https://github.com/meilisearch/meilisearch/pull/5783) No need to activate the [experimental feature](https://github.com/orgs/meilisearch/discussions/763) anymore to use this operator 🎉 - Docker image: sign container image using Cosign in keyless mode by [@&#8203;LeSuisse](https://github.com/LeSuisse) in [#&#8203;3265](https://github.com/meilisearch/meilisearch/pull/3265) ##### Bugs - Turn chat settings to `PATCH` by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5807](https://github.com/meilisearch/meilisearch/pull/5807) ⚠️ This fix leads to a breaking change on: `PUT` → `PATCH`. Integrations and SDKs will adapt to this change. - Fix `snapshotCreation` task being included in snapshot by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5773](https://github.com/meilisearch/meilisearch/pull/5773) ##### Maintenance - Tests & CI - Ignore yet another flaky test by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5740](https://github.com/meilisearch/meilisearch/pull/5740) - Fix Rails CI by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5756](https://github.com/meilisearch/meilisearch/pull/5756) - Use Server::wait\_task() instead of Index::wait\_task() by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5703](https://github.com/meilisearch/meilisearch/pull/5703) - Faster batches:: IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5626](https://github.com/meilisearch/meilisearch/pull/5626) - Adapt Go CI to recent change in the Go repo by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5790](https://github.com/meilisearch/meilisearch/pull/5790) - Bump svenstaro/upload-release-action from 2.11.1 to 2.11.2 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5795](https://github.com/meilisearch/meilisearch/pull/5795) - Bump sigstore/cosign-installer from 3.8.2 to 3.9.2 by [@&#8203;dependabot](https://github.com/dependabot)\[bot] in [#&#8203;5794](https://github.com/meilisearch/meilisearch/pull/5794) - Documentation - Release process change by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5766](https://github.com/meilisearch/meilisearch/pull/5766) - Minor fix in PR template by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5804](https://github.com/meilisearch/meilisearch/pull/5804) - Minor docs update by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5803](https://github.com/meilisearch/meilisearch/pull/5803) ### [`v1.16.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.16.0): 🦚 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.15.2...v1.16.0) Meilisearch v1.16 introduces two main features: multimodal embeddings and a new `/export` route. Multimodal embeddings use AI-powered search to index images in addition to textual documents. The `/export` route simplifies migrating from a local Meilisearch instance to Meilisearch Cloud. 🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment happens between 4 to 48 hours after a new version becomes available. Some SDKs might not include all new features. Consult the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️). ### New features and updates 🔥 #### Experimental feature: Multimodal embeddings v1.16 allows indexing and searching non-textual documents, as well as performing searches with image queries. This new feature uses multimodal embedders to provide a common semantic representation for images, texts, and any other piece of data. ##### Usage First, enable the `multimodal` experimental feature: ```sh curl \ -X PATCH 'MEILISEARCH_URL/experimental-features/' \ -H 'Content-Type: application/json' \ --data-binary '{ "multimodal": true }' ``` Next, pick an embedder provider that supports multimodal embeddings such as [Cohere](https://docs.cohere.com/v2/reference/embed) or [VoyageAI](https://docs.voyageai.com/docs/multimodal-embeddings) to start building the embedding configuration. The following is an example configuration for multimodal embedder using VoyageAI: ```sh curl \ -X PATCH 'MEILISEARCH_URL/indexes/INDEX_NAME/settings/embedders' \ -H 'Content-Type: application/json' \ --data-binary '{ "voyage": { "source": "rest", "url": "https://api.voyageai.com/v1/multimodalembeddings", "apiKey": "VOYAGE_API_KEY", "indexingFragments": { "text": { "value": { "content": [ { "type": "text", "text": "A movie titled {{doc.title}} whose description starts with {{doc.overview|truncateWords:20}}." } ] } }, "poster": { "value": { "content": [ { "type": "image_url", "image_url": "{{doc.poster}}" } ] } } }, "searchFragments": { "poster": { "value": { "content": [ { "type": "image_url", "image_url": "{{media.poster}}" } ] } }, "image": { "value": { "content": [ { "type": "image_base64", "image_base64": "data:{{media.image.mime}};base64,{{media.image.data}}" } ] } }, "text": { "value": { "content": [ { "type": "text", "text": "{{q}}" } ] } } }, "request": { "inputs": [ "{{fragment}}", "{{..}}" ], "model": "voyage-multimodal-3" }, "response": { "data": [ { "embedding": "{{embedding}}" }, "{{..}}" ] } }} ``` The configuration above sets up Meilisearch to generate vectors for two fields: `text` and `poster`. It also allows users to perform searches with an image URL, a raw image, or regular text. Use the new `media` search parameter together with one of the `searchFragments` you specified in your embedder to search with an image: ```sh curl -X POST 'MEILISEARCH_URL/indexes/INDEX_NAME/search' \ -H 'content-type: application/json' \ --data-binary '{ "media": { "poster": "https://image.tmdb.org/t/p/w500/pgqj7QoBPWFLLKtLEpPmFYFRMgB.jpg" }, "hybrid": { "embedder": "EMBEDDER_NAME" } }' ``` You can also perform a text search with `q` and `hybrid`: ```sh curl -X POST 'MEILISEARCH_URL/indexes/INDEX_NAME/search' \ -H 'content-type: application/json' \ --data-binary '{ "q": "A movie with lightsabers in space", "hybrid": { "embedder": "voyage", "semanticRatio": 0.5 } }' ``` Meilisearch performs searches all fields with embeddings when parsing `hybrid` queries targeting indexes with multimodal embedders. For more information about this feature, please refer to its [public usage page](https://meilisearch.notion.site/Multimodal-search-usage-1c14b06b651f80c1bf9effe56dbeef54) Done by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5596](https://github.com/meilisearch/meilisearch/pull/5596) #### The new `/export` route v1.16 introduces a new `/export` route that allows transferring documents between instances without having to create a dump or a snapshot. This feature is particularly useful when migrating from a local machine to Meilisearch Cloud. ##### Usage To transfer data between instances, query `/export` and point its `url` parameter to the URL of the target instance: ```sh curl \ -X POST 'MEILISEARCH_URL/export' \ -H 'Content-Type: application/json' \ --data-binary '{ "url": "http://localhost:7711" }' ``` This will generate an export and task start migrating data between instances. Depending on the target instance, you may also have to supply an API key with full admin permissions in the `apiKey` parameter. Consult the documentation for an exhaustive list of accepted parameters. If the request fails, Meilisearch will retry a few times before setting its status to failed. You may also cancel an export task manually. In this case, Meilisearch will interrupt the task locally, but not in the target instance. Done by [@&#8203;kerollmops](https://github.com/kerollmops) with the help of [@&#8203;mubelotix](https://github.com/mubelotix) in [#&#8203;5670](https://github.com/meilisearch/meilisearch/pull/5670) #### Other improvements - Add support for nested wildcards in `attributes_to_search_on` by [@&#8203;lblack00](https://github.com/lblack00) in [#&#8203;5548](https://github.com/meilisearch/meilisearch/pull/5548) - Improve support of geo field extraction from documents by [@&#8203;nnethercott](https://github.com/nnethercott) in [#&#8203;5592](https://github.com/meilisearch/meilisearch/pull/5592) - Use all CPUs when importing dumps by [@&#8203;nnethercott](https://github.com/nnethercott) in [#&#8203;5527](https://github.com/meilisearch/meilisearch/pull/5527) - Display the last embedder error live in batches by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5707](https://github.com/meilisearch/meilisearch/pull/5707) - Add fallback instance option to revert to old indexer by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5687](https://github.com/meilisearch/meilisearch/pull/5687) - Introduce filters in the chat completions by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5710](https://github.com/meilisearch/meilisearch/pull/5710) - Allow sorting on the /documents route by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5716](https://github.com/meilisearch/meilisearch/pull/5716) - A Read-Only Admin key will be created in new empty databases, to prevent accidentally writing to database while investigating, by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5693](https://github.com/meilisearch/meilisearch/pull/5693) - Use the edition 2024 documents indexer in the dumps by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5762](https://github.com/meilisearch/meilisearch/pull/5762) ### Fixes 🐞 - Improve the performance when managing single-typo words by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5551](https://github.com/meilisearch/meilisearch/pull/5551) - Fix distinct attribute functionality for hybrid search by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5614](https://github.com/meilisearch/meilisearch/pull/5614) - Fix bug related to Cyrillic having different typo tolerance due to byte counting bug by [@&#8203;arthurgousset](https://github.com/arthurgousset) in [#&#8203;5617](https://github.com/meilisearch/meilisearch/pull/5617) - Fix Gemini `base_url` when used with OpenAI clients by [@&#8203;diksipav](https://github.com/diksipav) in [#&#8203;5692](https://github.com/meilisearch/meilisearch/pull/5692) - Remove Gemini from LLM-providers list due to incompatibility with OpenAI by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5708](https://github.com/meilisearch/meilisearch/pull/5708) - Fix bug when using the environment variable for `--experimental-limit-batched-tasks-total-size` by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5705](https://github.com/meilisearch/meilisearch/pull/5705) - Fix `disableOnNumbers` not being affected by typo tolerance settings resets by [@&#8203;Nymuxyzo](https://github.com/Nymuxyzo) in [#&#8203;5702](https://github.com/meilisearch/meilisearch/pull/5702) - Make sure to recover from missing update files by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5683](https://github.com/meilisearch/meilisearch/pull/5683) - Add analytics to chat completions by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5709](https://github.com/meilisearch/meilisearch/pull/5709) - Fix: Preserve order of searchable attributes when modified by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5751](https://github.com/meilisearch/meilisearch/pull/5751) - Fix Total Hits being wrong when rankingScoreThreshold is used by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5725](https://github.com/meilisearch/meilisearch/pull/5725) - Fix incorrect document count in stats after clearing all documents by [@&#8203;kametsun](https://github.com/kametsun) in [#&#8203;5754](https://github.com/meilisearch/meilisearch/pull/5754) - Fix chat settings dumpless upgrade by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5761](https://github.com/meilisearch/meilisearch/pull/5761) - Fix panic when attempting to remove an embedder that does not exist by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5734](https://github.com/meilisearch/meilisearch/pull/5734) - Fixes an issue where sending searchParameters: `{}` in index chat settings would incorrectly set the limit to 20 instead of resetting to empty defaults - Update the mini-dashboard to v0.2.22 and fix a crash by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5798](https://github.com/meilisearch/meilisearch/pull/5798) ### Misc - Dependencies updates - Remove old dependencies by [@&#8203;Mubelotix](https://github.com/Mubelotix) in [#&#8203;5689](https://github.com/meilisearch/meilisearch/pull/5689) - Upgrade dependencies by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5686](https://github.com/meilisearch/meilisearch/pull/5686) - Bump the mini-dashboard to v0.2.20 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5728](https://github.com/meilisearch/meilisearch/pull/5728) - CIs and tests (34 PRs, one folk, yes!) - perf: Faster IT tests - stats.rs by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5572](https://github.com/meilisearch/meilisearch/pull/5572) - perf: Faster index::get\_index IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5578](https://github.com/meilisearch/meilisearch/pull/5578) - tests: Assert succeeded/failed for the index::delete\_index IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5580](https://github.com/meilisearch/meilisearch/pull/5580) - tests: Faster index::search::mod IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5584](https://github.com/meilisearch/meilisearch/pull/5584) - perf: Faster index::update\_index IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5579](https://github.com/meilisearch/meilisearch/pull/5579) - perf: Faster integration tests for add\_documents.rs by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5574](https://github.com/meilisearch/meilisearch/pull/5574) - tests: Faster search::errors IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5599](https://github.com/meilisearch/meilisearch/pull/5599) - tests: Faster search::locales IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5601](https://github.com/meilisearch/meilisearch/pull/5601) - tests: Faster search::matching\_strategy IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5602](https://github.com/meilisearch/meilisearch/pull/5602) - tests: search::pagination IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5604](https://github.com/meilisearch/meilisearch/pull/5604) - tests: Faster search::restricted\_searchable IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5605](https://github.com/meilisearch/meilisearch/pull/5605) - tests: Faster settings::distinct IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5606](https://github.com/meilisearch/meilisearch/pull/5606) - tests: Faster settings::proximity\_settings IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5609](https://github.com/meilisearch/meilisearch/pull/5609) - tests: Faster settings::tokenizer\_customization IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5610](https://github.com/meilisearch/meilisearch/pull/5610) - tests: Faster search::facet\_search IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5600](https://github.com/meilisearch/meilisearch/pull/5600) - tests: Faster settings::get\_settings IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5607](https://github.com/meilisearch/meilisearch/pull/5607) - tests: Faster vector::binary\_quantized IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5618](https://github.com/meilisearch/meilisearch/pull/5618) - tests: Faster search::distinct IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5620](https://github.com/meilisearch/meilisearch/pull/5620) - tests: Faster similar::errors IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5621](https://github.com/meilisearch/meilisearch/pull/5621) - tests: Faster documents::get\_documents IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5624](https://github.com/meilisearch/meilisearch/pull/5624) - tests: Faster documents::delete\_documents IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5619](https://github.com/meilisearch/meilisearch/pull/5619) - tests: Faster search::geo IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5623](https://github.com/meilisearch/meilisearch/pull/5623) - tests: Faster search::hybrid IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5625](https://github.com/meilisearch/meilisearch/pull/5625) - tests: Faster tasks::mod IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5615](https://github.com/meilisearch/meilisearch/pull/5615) - tests: Faster stats::mod IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5611](https://github.com/meilisearch/meilisearch/pull/5611) - tests: Faster search::filters IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5622](https://github.com/meilisearch/meilisearch/pull/5622) - tests: Use Server::wait\_task() instead of Index::wait\_task() in search:: by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5700](https://github.com/meilisearch/meilisearch/pull/5700) - tests: Use Server::wait\_task() instead of Index::wait\_task() in index:: by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5698](https://github.com/meilisearch/meilisearch/pull/5698) - tests: Use Server::wait\_task() instead of Index::wait\_task() in settings:: by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5699](https://github.com/meilisearch/meilisearch/pull/5699) - tests: Use Server::wait\_task() instead of Index::wait\_task() in documents:: by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5697](https://github.com/meilisearch/meilisearch/pull/5697) - tests: Faster documents::update\_documents IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5682](https://github.com/meilisearch/meilisearch/pull/5682) - tests: Faster similar::mod IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5680](https://github.com/meilisearch/meilisearch/pull/5680) - tests: Faster document::errors IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5677](https://github.com/meilisearch/meilisearch/pull/5677) - tests: Faster settings::prefix\_search\_settings IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5681](https://github.com/meilisearch/meilisearch/pull/5681) - tests: Faster search::multi IT tests by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5603](https://github.com/meilisearch/meilisearch/pull/5603) - Misc - Ignore flaky test by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5627](https://github.com/meilisearch/meilisearch/pull/5627) - ci: Use `GITHUB_TOKEN` secret for the `db change check` workflow by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5632](https://github.com/meilisearch/meilisearch/pull/5632) - chore: Fix English grammar in SearchQueue's comments by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5642](https://github.com/meilisearch/meilisearch/pull/5642) - Typo fix by [@&#8203;mcmah309](https://github.com/mcmah309) in [#&#8203;5589](https://github.com/meilisearch/meilisearch/pull/5589) - docs: Recommend using a custom path for the benches' data by [@&#8203;martin-g](https://github.com/martin-g) in [#&#8203;5672](https://github.com/meilisearch/meilisearch/pull/5672) ❤️ Thanks again to our external contributors: - [Meilisearch](https://github.com/meilisearch/meilisearch): [@&#8203;martin-g](https://github.com/martin-g), [@&#8203;lblack00](https://github.com/lblack00), [@&#8203;mcmah309](https://github.com/mcmah309), [@&#8203;nnethercott](https://github.com/nnethercott), [@&#8203;arthurgousset](https://github.com/arthurgousset), [@&#8203;Mubelotix](https://github.com/Mubelotix), [@&#8203;diksipav](https://github.com/diksipav), [@&#8203;Nymuxyzo](https://github.com/Nymuxyzo), [@&#8203;kametsun](https://github.com/kametsun) - [Arroy](https://github.com/meilisearch/arroy): [@&#8203;nnethercott](https://github.com/nnethercott) ### [`v1.15.2`](https://github.com/meilisearch/meilisearch/releases/tag/v1.15.2): 🦘 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.15.1...v1.15.2) This patch release introduces a major fix and some minor fixes. ##### Major fix: searchable attributes database bug Some searchable fields were removed from the searchable databases when they were removed from the `filterableAttributes` setting. This made them unsearchable, although they were still precise in the `searchableAttributes` setting. Fixed by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5660](https://github.com/meilisearch/meilisearch/pull/5660) ##### Minor fixes - Fix chat route missing base URL and Mistral error handling by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5665](https://github.com/meilisearch/meilisearch/pull/5665) - Various fixes to embedding regeneration by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5668](https://github.com/meilisearch/meilisearch/pull/5668) ### [`v1.15.1`](https://github.com/meilisearch/meilisearch/releases/tag/v1.15.1): 🦘 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.15.0...v1.15.1) Meilisearch v1.15.1 adds new experimental conversational features and enables LLM-driven chat features. 🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment takes 4 to 48 hours after a new version becomes available. Some SDKs might not include all new features. Please look over the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️). #### Chat with your indexes After enabling the experimental chat feature, you can create a chat workspace with the appropriate settings. We [have a guide](https://www.meilisearch.com/docs/guides/ai/getting_started_with_chat) on how to set up a good chat interface for your indexes. ```bash curl -X POST 'http://localhost:7700/chats/my-assistant/settings' \ -H 'Content-Type: application/json' \ -d '{ "source": "openAi", "apiKey": "sk-abc..." }' ``` Then by using the official OpenAI SDK you'll be able to chat with your indexes. ```javascript import OpenAI from 'openai'; const client = new OpenAI({ baseURL: 'http://localhost:7700/chats/my-assistant', apiKey: 'YOUR_MEILISEARCH_CHAT_API_KEY', }); const completion = await client.chat.completions.create({ model: 'gpt-3.5-turbo', messages: [{ role: 'user', content: 'What is Meilisearch?' }], stream: true, }); for await (const chunk of completion) { console.log(chunk.choices[0]?.delta?.content || ''); } ``` Done by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5556](https://github.com/meilisearch/meilisearch/pull/5556). ### [`v1.15.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.15.0): 🦘 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.14.0...v1.15.0) Meilisearch v1.15 adds a new typo tolerance setting, allowing you to disable typo tolerance for numbers. It also enables comparison operators for string filters. 🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment takes 4 to 48 hours after a new version becomes available. Some SDKs might not include all new features. Please look over the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️). ### New features and updates 🔥 #### Disable typo tolerance for numbers Set `typoTolerance.disableOnNumbers` to `true` to disable typo tolerance for numbers: ```bash curl -X POST 'http://localhost:7700/indexes/movies/settings' \ -H 'Content-Type: application/json' \ -d '{ "typoTolerance": {"disableOnNumbers": true} }' ``` Deactivating the typo tolerance on numbers can be helpful when trying to reduce false positives, such as a query term `2024` returning results that include `2025` and `2004`. It may also improve indexing performance. Done by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5494](https://github.com/meilisearch/meilisearch/pull/5494). #### Lexicographic string filters This release allows you to filter strings lexicographically by enabling comparison operators (<, <=, >, >=, TO) on string values: ```bash curl -X POST 'http://localhost:7700/indexes/movies/search' \ -H 'Content-Type: application/json' \ -d '{ "filter": "release_date >= '2024-06'" }' ``` This new feature can be particularly useful when filtering human-readable dates. Done by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5535](https://github.com/meilisearch/meilisearch/pull/5535). #### Other improvements - Allows cancelling an upgrade to a new Meilisearch version by rolling back all upgraded indexes by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5523](https://github.com/meilisearch/meilisearch/pull/5523) - Support EC private key as SSL certificate by [@&#8203;HDT3213](https://github.com/HDT3213) in [#&#8203;5471](https://github.com/meilisearch/meilisearch/pull/5471) - When passing the relevant [CLI option](https://github.com/orgs/meilisearch/discussions/833), stop compacting snapshots, to speed up their generation by [@&#8203;dureuill](https://github.com/dureuill) and [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5498](https://github.com/meilisearch/meilisearch/pull/5498) and [#&#8203;5560](https://github.com/meilisearch/meilisearch/pull/5560) - Add new `batchStrategy` field in the batches stats by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5488](https://github.com/meilisearch/meilisearch/pull/5488), [#&#8203;5530](https://github.com/meilisearch/meilisearch/pull/5530), and [#&#8203;5588](https://github.com/meilisearch/meilisearch/pull/5588) - Add log field tracking time spent searching in the vector store by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5525](https://github.com/meilisearch/meilisearch/pull/5525) - Improve filterable error messages by [@&#8203;CodeMan62](https://github.com/CodeMan62) in [#&#8203;5425](https://github.com/meilisearch/meilisearch/pull/5425) - Improve error messages on embeddings dimension mismatch by [@&#8203;vuthanhtung2412](https://github.com/vuthanhtung2412) in [#&#8203;5449](https://github.com/meilisearch/meilisearch/pull/5449) - Update `/network` URL validation error message format by [@&#8203;CodeMan62](https://github.com/CodeMan62) in [#&#8203;5486](https://github.com/meilisearch/meilisearch/pull/5486) - Expose the task queue's status size in the Prometheus metrics by [@&#8203;DanasFi](https://github.com/DanasFi) in [#&#8203;5512](https://github.com/meilisearch/meilisearch/pull/5512) ### Fixes 🐞 - Fix `_matchesPosition` length calculation to improve client-side cropping by [@&#8203;shaokeyibb](https://github.com/shaokeyibb) in [#&#8203;5446](https://github.com/meilisearch/meilisearch/pull/5446) - Fix `_geo` ranking rule by [@&#8203;HDT3213](https://github.com/HDT3213) in [#&#8203;5487](https://github.com/meilisearch/meilisearch/pull/5487) - Fix a panic in the search that could happen when looking for typos with a search prefix having more than 65k possible hits in the DB by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5564](https://github.com/meilisearch/meilisearch/pull/5564) - Make sure that passing `MEILI_EXPERIMENTAL_MAX_NUMBER_OF_BATCHED_TASKS` to 0 results in Meilisearch never processing any kind of task. By [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5565](https://github.com/meilisearch/meilisearch/pull/5565) - Forbid value `0` for `maxTotalHits` in the index settings by [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5566](https://github.com/meilisearch/meilisearch/pull/5566) - No longer reject `documentTemplate`s that use array filters on documents (e.g. `join`) by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5593](https://github.com/meilisearch/meilisearch/pull/5593) ### Misc - Dependency updates - Update Rust to 1.85.1 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5480](https://github.com/meilisearch/meilisearch/pull/5480) - Update charabia v0.9.3 by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5466](https://github.com/meilisearch/meilisearch/pull/5466) - Update the Prometheus to fix a security vulnerability by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5513](https://github.com/meilisearch/meilisearch/pull/5513) - CIs and tests - Setup the Milestone CI to update the Ruleset by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5444](https://github.com/meilisearch/meilisearch/pull/5444) - Make the CI work with GitHub's merge queue grouping by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5445](https://github.com/meilisearch/meilisearch/pull/5445) - Remove Bors references from the repository by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5447](https://github.com/meilisearch/meilisearch/pull/5447) - Split unit tests for tasks by [@&#8203;shu-kitamura](https://github.com/shu-kitamura) in [#&#8203;5424](https://github.com/meilisearch/meilisearch/pull/5424) - Misc - Improve dumpless upgrade compatibility by [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5395](https://github.com/meilisearch/meilisearch/pull/5395) - Fix links and formatting in README for clarity and consistency by [@&#8203;ZeroZ-lab](https://github.com/ZeroZ-lab) in [#&#8203;5533](https://github.com/meilisearch/meilisearch/pull/5533) ❤️ Thanks again to our external contributors: - [Meilisearch](https://github.com/meilisearch/meilisearch): [@&#8203;shu-kitamura](https://github.com/shu-kitamura), [@&#8203;shaokeyibb](https://github.com/shaokeyibb), [@&#8203;CodeMan62](https://github.com/CodeMan62), [@&#8203;vuthanhtung2412](https://github.com/vuthanhtung2412), [@&#8203;HDT3213](https://github.com/HDT3213), [@&#8203;DanasFi](https://github.com/DanasFi), and [@&#8203;ZeroZ-lab](https://github.com/ZeroZ-lab). - [Charabia](https://github.com/meilisearch/charabia): [@&#8203;luflow](https://github.com/luflow), [@&#8203;mosuka](https://github.com/mosuka), and [@&#8203;HDT3213](https://github.com/HDT3213). - [RoaringBitmap](https://github.com/RoaringBitmap/roaring-rs): [@&#8203;lucascool12](https://github.com/lucascool12) and [@&#8203;Dr-Emann](https://github.com/Dr-Emann). ### [`v1.14.0`](https://github.com/meilisearch/meilisearch/releases/tag/v1.14.0): 🦫 [Compare Source](https://github.com/meilisearch/meilisearch/compare/v1.13.3...v1.14.0) Meilisearch v1.14 gives more granular control over which parts of filters you can disable for indexing performance optimization. This release also includes composite embedders, which can improve embedding generation during search and indexing, and a new route to retrieve multiple documents by their IDs. 🧰 All official Meilisearch integrations (including SDKs, clients, and other tools) are compatible with this Meilisearch release. Integration deployment happens between 4 to 48 hours after a new version becomes available. Some SDKs might not include all new features. Consult the project repository for detailed information. Is a feature you need missing from your chosen SDK? Create an issue letting us know you need it, or, for open-source karma points, open a PR implementing it (we'll love you for that ❤️). ### New features and updates 🔥 #### Granular filterable attribute settings v1.14 gives you more control over which types of filter you want to disable in your searches. This allows you to further optimize indexing speeds by letting you activate only the filter features you need. Use `PATCH /indexes/INDEX_NAME/settings` to specify which filters you want to enable for each attribute in your documents: ```json { "filterableAttributes": [ { "attributePatterns": ["genre", "artist"], "features": { "facetSearch": true, "filter": { "equality": true, "comparison": false } } }, { "attributePatterns": ["rank"], "features": { "facetSearch": false, "filter": { "equality": true, "comparison": true } } } ] } ``` For more details about this feature, please refer to [the dedicated documentation page](https://www.meilisearch.com/docs/reference/api/settings#filterable-attribute-object). Done by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5254](https://github.com/meilisearch/meilisearch/pull/5254). #### Composite embedders This feature allows using different embedders at search and indexing time. This can be useful when optimizing AI-powered search performance. For example, you may prefer to use: - A remote embedder during indexing, as remote embedders have higher bandwidth and can generate more embeddings per second - A local embedder when answering to search queries, as local embedders have lower latency and can respond more quickly to user input To use the feature, follow these steps: 1. Enable the `Composite embedders` feature with the Meilisearch Cloud interface, or with the `/experimental-features` route: ```sh curl MEILISEARCH_URL/experimental-features \ -H 'Content-Type: application/json' \ -d '{"compositeEmbedders": true}' ``` 2. Next, create an embedder, setting its `source` to `"composite"` and defining one `searchEmbedder` and one `indexingEmbedder`: ```jsonc { "embedders": { "text": { "source": "composite", "searchEmbedder": { "source": "huggingFace", "model": "baai/bge-base-en-v1.5", "revision": "a5beb1e3e68b9ab74eb54cfd186867f64f240e1a" }, "indexingEmbedder": { "source": "rest", "url": "https://URL.endpoints.huggingface.cloud", "apiKey": "hf_XXXXXXX", "documentTemplate": "Your {{doc.template}}", "request": { "inputs": [ "{{text}}", "{{..}}" ] }, "response": [ "{{embedding}}", "{{..}}" ] } } } } ``` 3. Once the composite embedder has been created, Meilisearch will use its `indexingEmbedder` during indexing and `searchEmbedder` when responding to user queries For more details about this feature, please refer to its [public usage page](https://www.notion.so/meilisearch/Composite-embedder-usage-14a4b06b651f81859dc3df21e8cd02a0?pvs=4#19f4b06b651f809ab3ecc0daae7d5856). Done by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5371](https://github.com/meilisearch/meilisearch/pull/5371) and [#&#8203;5401](https://github.com/meilisearch/meilisearch/pull/5401). #### Retrieve multiple documents by ID It is now possible to retrieve multiple documents by their IDs: ``` curl -H 'Content-Type: application/json' MEILISEARCH_URL/indexes/INDEX_UID/documents -d '{ "ids": ["cody", "finn", "brandy", "gambit"] }' ``` ```json { "results": [ { "id": "brandy", "info": 13765493 }, { "id": "finn", "info": 35863 }, { "id": "cody", "info": 122263 }, { "id": "gambit", "info": 22222 } ], "offset": 0, "limit": 20, "total": 4 } ``` > \[!WARNING] > Documents are *not* returned in the queried order. Non-existent documents are ignored. Done by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5384](https://github.com/meilisearch/meilisearch/pull/5384). #### Other improvements - Batch together `/documents` requests using either `PUT` or `POST` by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5293](https://github.com/meilisearch/meilisearch/pull/5293) - Display timestamped internal indexing steps on the `/batches` route by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5356](https://github.com/meilisearch/meilisearch/pull/5356) and [#&#8203;5364](https://github.com/meilisearch/meilisearch/pull/5364) - Introduce `exhaustiveFacetCount` parameter to `/facet-search` route to retrieve an exhaustive facet count by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5369](https://github.com/meilisearch/meilisearch/pull/5369) - Reduce RAM consumption of arroy by [@&#8203;irevoire](https://github.com/irevoire) in [meilisearch/arroy#105](https://github.com/meilisearch/arroy/pull/105) - Experimental feature: Cache embeddings during search (Read more in the [feature discussion](https://github.com/orgs/meilisearch/discussions/818)) by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5418](https://github.com/meilisearch/meilisearch/pull/5418) - Extend batch progress view to include indexing of vectors by [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5420](https://github.com/meilisearch/meilisearch/pull/5420) - Armenian characters are no longer case-sensitive by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5454](https://github.com/meilisearch/meilisearch/pull/5454) - Avoid reindexing searchables when the order changes by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5402](https://github.com/meilisearch/meilisearch/pull/5402) - Accept cancellation tasks even when the disk is full by [@&#8203;irevoire](https://github.com/irevoire) in [#&#8203;5492](https://github.com/meilisearch/meilisearch/pull/5492) ### Fixes - Geo update bug by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5407](https://github.com/meilisearch/meilisearch/pull/5407) - Fix prefix search on attributes listed in `disabledOnAttributes` settings by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5415](https://github.com/meilisearch/meilisearch/pull/5415) (fixes [#&#8203;5347](https://github.com/meilisearch/meilisearch/issues/5347) and [#&#8203;5452](https://github.com/meilisearch/meilisearch/issues/5452)) - Fix CI to work with merge queues by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5456](https://github.com/meilisearch/meilisearch/pull/5456) - Support fetching the pooling method from the model configuration by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5355](https://github.com/meilisearch/meilisearch/pull/5355) - Delete unused prefixes by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5413](https://github.com/meilisearch/meilisearch/pull/5413) - Fixes mini dashboard to prevent the panel from popping up every time by [@&#8203;curquiza](https://github.com/curquiza) in [#&#8203;5436](https://github.com/meilisearch/meilisearch/pull/5436) - Enabling `rankingScoreThreshold` no longer causes `_rankingScore` to be miscalculated by [@&#8203;barloes](https://github.com/barloes) and [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5313](https://github.com/meilisearch/meilisearch/pull/5313) - Validate dimensions of embedding when receiving documents with `_vectors` by [@&#8203;dureuill](https://github.com/dureuill) in [#&#8203;5478](https://github.com/meilisearch/meilisearch/pull/5478) ### Misc - Dependencies updates - Bump Ubuntu in the CI from 20.04 to 22.04 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5338](https://github.com/meilisearch/meilisearch/pull/5338) - Bump heed to v0.22 by [@&#8203;irevoire](https://github.com/irevoire) and [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5406](https://github.com/meilisearch/meilisearch/pull/5406) - Bump ring to v0.17.14 to compile on old aarch64 by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5423](https://github.com/meilisearch/meilisearch/pull/5423) - Bump zip from 2.2.2 to 2.3.0 by [@&#8203;dependabot](https://github.com/dependabot) in [#&#8203;5426](https://github.com/meilisearch/meilisearch/pull/5426) - CIs and tests - Improve test performance of get\_index.rs by [@&#8203;DerTimonius](https://github.com/DerTimonius) in [#&#8203;5210](https://github.com/meilisearch/meilisearch/pull/5210) - Ollama Integration Tests by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5308](https://github.com/meilisearch/meilisearch/pull/5308) - Ensure the settings routes are properly configured when a new field is added to the Settings struct by [@&#8203;MichaScant](https://github.com/MichaScant) in [#&#8203;5149](https://github.com/meilisearch/meilisearch/pull/5149) - Skip a snapshot test on Windows by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5383](https://github.com/meilisearch/meilisearch/pull/5383) - Fix CI to work with merge queues by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5456](https://github.com/meilisearch/meilisearch/pull/5456) - Accept total batch size in human size by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5421](https://github.com/meilisearch/meilisearch/pull/5421) - Add more progress levels to measure merging and post-processing by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5422](https://github.com/meilisearch/meilisearch/pull/5422) and [#&#8203;5468](https://github.com/meilisearch/meilisearch/pull/5468) - Isolate word fst usage to dedicate it to typo-correction by [@&#8203;ManyTheFish](https://github.com/ManyTheFish) in [#&#8203;5415](https://github.com/meilisearch/meilisearch/pull/5415) - Show database sizes batches by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5457](https://github.com/meilisearch/meilisearch/pull/5457) and [#&#8203;5464](https://github.com/meilisearch/meilisearch/pull/5464) > ⚠️ Please consider that the batches stats content can change anytime. - Improve performance of computing document stats by [@&#8203;Kerollmops](https://github.com/Kerollmops) in [#&#8203;5465](https://github.com/meilisearch/meilisearch/pull/5465) ❤️ Thanks again to our external contributors: - [Meilisearch](https://github.com/meilisearch/meilisearch): [@&#8203;MichaScant](https://github.com/MichaScant) - [Heed](https://github.com/meilisearch/heed): [@&#8203;oXtxNt9U](https://github.com/oXtxNt9U) - [Arroy](https://github.com/meilisearch/arroy): [@&#8203;ptondereau](https://github.com/ptondereau) - [Charabia](https://github.com/meilisearch/charabia): [@&#8203;NarHakobyan](https://github.com/NarHakobyan), [@&#8203;mosuka](https://github.com/mosuka) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "on the first day of the month" - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNC45IiwidXBkYXRlZEluVmVyIjoiNDQuMTQuOSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/getmeili-meilisearch-1.x:renovate/getmeili-meilisearch-1.x
git switch renovate/getmeili-meilisearch-1.x

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff renovate/getmeili-meilisearch-1.x
git switch renovate/getmeili-meilisearch-1.x
git rebase main
git switch main
git merge --ff-only renovate/getmeili-meilisearch-1.x
git switch renovate/getmeili-meilisearch-1.x
git rebase main
git switch main
git merge --no-ff renovate/getmeili-meilisearch-1.x
git switch main
git merge --squash renovate/getmeili-meilisearch-1.x
git switch main
git merge --ff-only renovate/getmeili-meilisearch-1.x
git switch main
git merge renovate/getmeili-meilisearch-1.x
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sophie/homelab!33
No description provided.