-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes regarding Meilisearch v1.3.0 #280
Labels
Meilisearch bump
Changes related to the Meilisearch bump version
Comments
brunoocasali
added
the
Meilisearch bump
Changes related to the Meilisearch bump version
label
Jul 5, 2023
This was referenced Jul 5, 2023
Merged
Merged
Closed
Closed
Closed
meili-bors bot
added a commit
to meilisearch/meilisearch-php
that referenced
this issue
Jul 31, 2023
539: Changes related to the next Meilisearch release (v1.3.0) r=brunoocasali a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: Bruno Casali <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-python
that referenced
this issue
Jul 31, 2023
797: Changes related to the next Meilisearch release (v1.3.0) r=alallema a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: Paul Sanders <[email protected]> Co-authored-by: Amélie <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-java
that referenced
this issue
Jul 31, 2023
620: Changes related to the next Meilisearch release (v1.3.0) r=alallema a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: alallema <[email protected]> Co-authored-by: Amélie <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-js
that referenced
this issue
Jul 31, 2023
1530: Changes related to the next Meilisearch release (v1.3.0) r=bidoubiwa a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: cvermand <[email protected]> Co-authored-by: Charlotte Vermandel <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-js-plugins
that referenced
this issue
Aug 1, 2023
1186: Changes related to the next Meilisearch release (v1.3.0) r=bidoubiwa a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: cvermand <[email protected]>
meili-bors bot
added a commit
to meilisearch/meilisearch-ruby
that referenced
this issue
Aug 2, 2023
452: Changes related to the next Meilisearch release (v1.3.0) r=brunoocasali a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: Bruno Casali <[email protected]>
Code-samples: #282 |
meili-bors bot
added a commit
to meilisearch/meilisearch-rust
that referenced
this issue
Aug 7, 2023
491: Changes related to the next Meilisearch release (v1.3.0) r=bidoubiwa a=meili-bot Related to this issue: meilisearch/integration-guides#280 This PR: - gathers the changes related to the next Meilisearch release (v1.3.0) so that this package is ready when the official release is out. - should pass the tests against the [latest pre-release of Meilisearch](https://github.com/meilisearch/meilisearch/releases). - might eventually contain test failures until the Meilisearch v1.3.0 is out.⚠️ This PR should NOT be merged until the next release of Meilisearch (v1.3.0) is out. _This PR is auto-generated for the [pre-release week](https://github.com/meilisearch/integration-guides/blob/main/resources/pre-release-week.md) purpose._ Co-authored-by: meili-bot <[email protected]> Co-authored-by: Charlotte Vermandel <[email protected]>
Missing issues to be opened in the non-updated SDKs before closing this issue |
This was referenced Aug 8, 2023
I am closing this issue since all the missing features are now tracked into each SDK. Thanks, team! 🦖 🎉 |
This was referenced Aug 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue gathers the changes related to the v1.3.0 of Meilisearch that will impact the integrations team.
📅 Release date: July 31th, 2023
The whole milestone of v1.3.0 is here!
tier #1
. Some of the features described may be done fortier #2
but will not be ready for the release day. Check the features below to understand which tier will receive which feature.🖖 Click here to check the current tiers state of the integrations:
Understand everything about tiers here.
[EXPERIMENTAL] Vector Store
Related to:
EXPERIMENTAL
specifications#248It allows the user to store dense vectors to be retrieved later during search time.
What needs to be changed:
vector
key during the search works:client.index('myindex').search('query', { vector: [0.1, ...] })
_vectors
special field in the documents:client.index('myindex').add_documents({ _vectors: [0.1, ...] })
vector
key similar to theq
key.PATCH /experimental-features
with{ "vectorStore": true }
Extra: Add inline documentation for the method, explaining the availability of this feature only for Meilisearch v1.3 and newer. And that is also an experimental feature that needs to be opt-in manually using the
/experimental-features
meilisearch/meilisearch#3857 endpoint.🤩 Affected integrations: All the integrations from
tier #1
andtier #2
(Python).Define fields to search on at search-time
Related to:
Add support for receiving a new key,
attributesToSearchOn
(which is an array of field names), that will enable running searches over a subset ofsearchableAttributes
without modifying Meilisearch’s index settings.🤩 Affected integrations: All the integrations from
tier #1
.Display hits' ranking scores
Related to:
This feature aims to return ranking details for each document to understand and tweak the score of the documents more efficiently.
Ensure the SDKs can handle the new search parameter
showRankingScore
. Also, ensure the SDK can handle the_rankingScore
attribute in the matchedhits
.🤩 Affected integrations: All the integrations from
tier #1
.[EXPERIMENTAL] Display ranking details at search
Related to:
This feature aims to return ranking details for each document to understand and tweak the score of the documents more easily.
Ensure the SDKs can handle the new search parameter
showRankingScoreDetails
. Also ensure the SDK can handle the_rankingScoreDetails
attributes in the matchedhits
.PATCH /experimental-features
with{ "scoreDetails": true }
Extra: Add inline documentation for the method, explaining the availability of this feature only for Meilisearch v1.3 and newer. And that is also an experimental feature that must be manually opt-in using the
/experimental-features
meilisearch/meilisearch#3857 endpoint.🤩 Affected integrations: All the integrations from
tier #1
.Sort facets value by alphanumerical or count order
Related to:
Adds the ability to sort facets by their value which could be by using
alpha
orcount
.Ensure the SDKs can handle the new index faceting configuration attribute
sortFacetValuesBy
. This enum could only takecount
oralpha
.The faceting configuration now have two attributes:
🤩 Affected integrations: All the integrations from
tier #1
.Search in facet values
Related to:
Users of bigger datasets could have difficulty interacting with vast lists of facets data since, until today, it was not possible to search on them.
To introduce this feature into the SDKs, we must:
Create a new method called
facetSearch(facetSearchQuery)
/facet_search(facetSearchQuery)
Besides all the other parameters that a regular
SearchQuery
can take. The newFacetSearchQuery
can take afacetName
,facetQuery
,filter
,q
,matchingStrategy
.Params definition:
🤩 Affected integrations: All the integrations from
tier #1
.Total Tasks in task route
Related to:
Returns the total number of tasks matching the filters on the
GET /tasks
route.Ensure the SDKs can handle the new get tasks response field
total
.🤩 Affected integrations: All the integrations from
tier #1
.The text was updated successfully, but these errors were encountered: