Updated tokenizer to better matching when search for code snippets #32261
+55
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Bruno Sofiato <[email protected]>
GiteaBot
added
the
lgtm/need 2
pull-request-size
bot
added
the
size/M
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR improves the accuracy of Gitea's code search.
Currently, Gitea does not consider statements such as
onsole.log("hello")as hits when the user searches forlog. The culprit is how both ES and Bleve are tokenizing the file contents (in both cases,console.logis a whole token).In ES' case, we changed the tokenizer to simple_pattern_split. In such a case, tokens are words formed by digits and letters. In Bleve's case, it employs a letter tokenizer.
P.S. I didn't change the index version since this index version is still unreleased.
Resolves #32220