-
Notifications
You must be signed in to change notification settings - Fork 45
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
Chinese / Japanese / Korean tokenizer support for search / tantivy #882
Comments
Another possible approach:
|
That would work as a fallback, but it would not integrate with the front-end. I think AtomicServer should provide a good out-of-the-box experience. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Out of the box, Tantivy only support latin languages. We could add some extra tokenizers:
Chinese (tantivy-jieba and cang-jie), Japanese (lindera, Vaporetto, and tantivy-tokenizer-tiny-segmenter) and Korean (lindera + lindera-ko-dic-builder)
I'm not sure if tokenizers can be combined. It doesn't look like it...
Tokenizer-specific fields
Problem with this approach is that it is very inefficient, it makes the search DB way bigger for every extra tokenizer we have
One Tokenizer To Rule Them All
Not sure if this is possible. We now use the
SimpleTokenizer
, but that is apparently not good for Chinese chars.Select tokenizer as config option
We can make the user decide when booting up AtomicServer.
This would add some code complexity.
It would not work for mixed language instances.
The text was updated successfully, but these errors were encountered: