You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue gathers the changes related to the v1.11.0 of Meilisearch that will impact the integrations scope.
📅 Release date: 28 October 2024
Timelines & steps
Pre-release
With the help of the changelog & this CI, define which integrations should be updated and how (New feature? Update README? Update tests?)
Fill in the "What to implement?" section below in this issue 👇. Minial implementation: PHP, JS, Instant-meilisearch.
Open implementation issues in repositories that need implementation.
Discuss with the Product team if needed. At least share this issue to let them know about the decisions.
Create a branch by running Octopus script: only open branches for the integrations we choose to update (defined in the previous step) + Kubernetes repository + Cloud provider repository (changing the version)
Update integrations according to the decisions (cf "What to implement?" section below in this issue 👇) ⚠️ If possible, this step is done before pre-release, once the feature is ready thanks to the prototype released by the engine team
JS: implementation + fix tests
PHP: implementation + fix tests
Go: Fix AI tests (maybe implementation is required)
Python: fix AI tests (maybe implementation is required)
Ruby: fix AI tests
Add code samples for the chosen up-to-date integrations with the new version of Meilisearch
Update the library version of the related integrations and prepare the changelogs
Release day
Release the integrations
Release JS
Release PHP
Go
Python
Ruby
Release Instant-meilisearch with new version of meilisearch-js
When using the semantic or the hybrid search, hybrid.embedder is now a mandatory parameter in GET and POST /indexes/{:indexUid}/search
As a consequence, it is now mandatory to pass hybrid even for full-vector search (with only vector and not q)
embedder is now a mandatory parameter in GET and POST /indexes/{:indexUid}/similar
Ignore non-zero semanticRatio when vector is passed but not q: a semantic search will be performed.
Changes:
A new sub setting in embedders setting to enable binary quantization and speed up indexing speed.
The default model for OpenAI is now text-embedding-3-small instead of text-embedding-ada-002.
Limit the maximum length of a rendered document template: when the source of an embedder is set to huggingFace, openAi, rest or ollama, then documentTemplateMaxBytes is now available as an optional parameter. This parameter describes the number of bytes in which the rendered document template text should fit when trying to embed a document. Longer texts are truncated to fit.
Add the ability to query whether a field is searchable in documentTemplate: use field.is_searchable: true if the field is a searchable attribute, otherwise false.
Request facet distributions and facet stats in your federated search, by using federation.facetsByIndex in the POST POST /multi-search route.
Merge the returned facets in a single facet distribution and stats that is global to the entire request, by using federation.mergeFacets in the POST POST /multi-search route.
This issue gathers the changes related to the v1.11.0 of Meilisearch that will impact the integrations scope.
📅 Release date: 28 October 2024
Timelines & steps
Pre-release
Release day
What to implement?
Experimental - AI search changes
Related issue in the engine:
Breaking:
hybrid.embedder
is now a mandatory parameter inGET and POST /indexes/{:indexUid}/search
hybrid
even for full-vector search (with onlyvector
and notq
)embedder
is now a mandatory parameter inGET and POST /indexes/{:indexUid}/similar
semanticRatio
whenvector
is passed but notq
: a semantic search will be performed.Changes:
embedders
setting to enable binary quantization and speed up indexing speed.text-embedding-3-small
instead oftext-embedding-ada-002
.huggingFace
,openAi
,rest
orollama
, thendocumentTemplateMaxBytes
is now available as an optional parameter. This parameter describes the number of bytes in which the rendered document template text should fit when trying to embed a document. Longer texts are truncated to fit.documentTemplate
: usefield.is_searchable
:true
if the field is a searchable attribute, otherwisefalse
.TODO:
Support facet distribution for federated search
Related issue in the engine: meilisearch/meilisearch#4932
federation.facetsByIndex
in the POSTPOST /multi-search
route.federation.mergeFacets
in the POSTPOST /multi-search
route.TODO:
Experimental - STARTS_WITH operator
Related issue in the engine: meilisearch/meilisearch#4872
Filter with the newly introduced
STARTS_WITH
operatorTODO:
Language setting enhancement: support ISO-639-1 languages code
Related issue in the engine: meilisearch/meilisearch#4827
TODO:
The text was updated successfully, but these errors were encountered: