-
Notifications
You must be signed in to change notification settings - Fork 102
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
Properly handle autocompletion with CJK using CJKUnigram filter #2712
Comments
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 9, 2024
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 9, 2024
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 9, 2024
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 9, 2024
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 9, 2024
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 14, 2024
…ationDB#2712 Auto complete matching need to use the index analyzer instead of default analyzer FoundationDB#2720
qdnguyen0
added a commit
to qdnguyen0/fdb-record-layer
that referenced
this issue
May 16, 2024
…ationDB#2712 Auto complete matching need to use the index analyzer instead of default analyzer FoundationDB#2720
MMcM
pushed a commit
that referenced
this issue
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For CJK, a prefix search like AB* would not return ABC since Lucene does not run AB* through an analyzer.
For this, we would need to split into (A and B*), using a CJKUnigram filter
The phrase search construction logic needs to be fixed
The text was updated successfully, but these errors were encountered: