Skip to content
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

Meilisearch: require all query terms to be matched #28293

Merged
merged 1 commit into from
Nov 29, 2023

Conversation

brechtvl
Copy link
Contributor

Previously only the first term had to be matched. That default Meilisearch behavior makes sense for e.g. some kind of autocomplete to find and select a single result. But for filtering issues it means you can't narrow down results by adding more terms.

This is also more consistent with other indexers and GitHub.


Reference:
https://www.meilisearch.com/docs/reference/api/search#matching-strategy

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Nov 29, 2023
@pull-request-size pull-request-size bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 29, 2023
Previously only the first term had to be matched. That default meilisearch
behavior makes sense for e.g. some kind of autocomplete to find and select
a single result. But for filtering issues it means you can't narrow down
results by adding more terms.

This is also more consistent with other indexers and GitHub.
@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Nov 29, 2023
@wxiaoguang wxiaoguang added the backport/v1.21 This PR should be backported to Gitea 1.21 label Nov 29, 2023
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Nov 29, 2023
@lunny lunny added the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Nov 29, 2023
@lunny lunny merged commit a7de14e into go-gitea:main Nov 29, 2023
25 checks passed
@GiteaBot GiteaBot added this to the 1.22.0 milestone Nov 29, 2023
@GiteaBot GiteaBot removed the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Nov 29, 2023
GiteaBot pushed a commit to GiteaBot/gitea that referenced this pull request Nov 29, 2023
Previously only the first term had to be matched. That default
Meilisearch behavior makes sense for e.g. some kind of autocomplete to
find and select a single result. But for filtering issues it means you
can't narrow down results by adding more terms.

This is also more consistent with other indexers and GitHub.

---

Reference:
https://www.meilisearch.com/docs/reference/api/search#matching-strategy
@GiteaBot GiteaBot added the backport/done All backports for this PR have been created label Nov 29, 2023
jolheiser pushed a commit that referenced this pull request Nov 29, 2023
Co-authored-by: Brecht Van Lommel <brecht@blender.org>
zjjhot added a commit to zjjhot/gitea that referenced this pull request Dec 1, 2023
* giteaofficial/main:
  Read `previous` info from git blame (go-gitea#28306)
  Add missing variable in tag list (go-gitea#28305)
  Make pushUpdate error verbose (go-gitea#28263)
  Meilisearch: require all query terms to be matched (go-gitea#28293)
  Ignore "non-existing" errors when getDirectorySize calculates the size (go-gitea#28276)
fuxiaohei pushed a commit to fuxiaohei/gitea that referenced this pull request Jan 17, 2024
Previously only the first term had to be matched. That default
Meilisearch behavior makes sense for e.g. some kind of autocomplete to
find and select a single result. But for filtering issues it means you
can't narrow down results by adding more terms.

This is also more consistent with other indexers and GitHub.

---

Reference:
https://www.meilisearch.com/docs/reference/api/search#matching-strategy
silverwind pushed a commit to silverwind/gitea that referenced this pull request Feb 20, 2024
Previously only the first term had to be matched. That default
Meilisearch behavior makes sense for e.g. some kind of autocomplete to
find and select a single result. But for filtering issues it means you
can't narrow down results by adding more terms.

This is also more consistent with other indexers and GitHub.

---

Reference:
https://www.meilisearch.com/docs/reference/api/search#matching-strategy
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Feb 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/done All backports for this PR have been created backport/v1.21 This PR should be backported to Gitea 1.21 lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants