Ticket search returns almost no ticket #22714
Comments
lunny
added a commit
that referenced
this issue
Feb 12, 2023
Fixes #22714 ### Changes: 1. Add a token filter which named "camelCase" between custom unicode token filter and "to_lower" token filter when add custom analyzer. ### Notice: If users want this feature to work, they should delete folder under {giteaPath}/data/indexers and restart application. Then application will create a new IndexMapping. ### Screenshots:  ### Others: I originally attempted to give users the ability to configure the "token_filters" in the "app.ini" file. But I found that if users does not strictly follow a right order to register "token_filters", they won't get the expected results. I think it is difficult to ask users to do this. So I finally give up this idea. --------- Co-authored-by: Jason Song <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Hi
Using Gitea 1.18.3 self-hosted on Debian 11 for a while, with a dozen of repos, we have just realized than searching through tickets returns no data or only a very-limited subset of data.
Ex: On a newly created repo, I create two tickets "Ticket Wednesday" and "NewTicket2", and search for keyword "Ticket". Only the first one is returned. If I add extra space in the second ("New Ticket 2"), it is then returned.
Ex: On another repo, I have two tickets whose title mentions the name "Server". Only one of the two is returned, whatever the wording (with space or not, etc.) of the second.
There is nothing wrong in /var/log/gitea/gitea.log not in access.log...
Do I need to activate something to allow searches?
Thank you for your help
Gitea Version
1.18.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
With these issues in my repo:
My search for "Ticket" returns
Git Version
2.30.2
Operating System
Debian 11
How are you running Gitea?
downloaded binary from gitea website
Database
MySQL
The text was updated successfully, but these errors were encountered: