feat(search): allow database fulltext index using custom parser #7074
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
Mmx233
force-pushed
the
feat/fulltext-ngram
branch
from
3648d3e
to
0232f9c
Compare
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.
The Ngram Parser can be used directly in MySQL 8.0 and above. In addition, both MySQL and Postgres can utilize various plugins to enhance tokenization for different languages.
This PR adds field
Parser string `json:"parser" env:"PARSER"`inconf.Conf.Databaseto allow admin custom parser for database fulltext index. Although only system admin can set this setting via the config file or environment variables, I want to make it clear that this field is not SQL safe and could be used to implement SQL injection.The changes in this PR have tested in:
ngram