-
Notifications
You must be signed in to change notification settings - Fork 25.2k
analyzer
not being applied to search time
#144
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
Comments
Doh of course - it would only be analyzed if passed in as a query string, not as a term. closing |
Yea, but note that there is the |
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we remove all leftover references to trial timestamp and replace it with the new name race timestamp. Relates elastic#128 Relates elastic#143 Relates elastic#144
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hiya
It may be something else, but it looks like the
analyzer
defined in the mapping is being applied at index time, but not at search time:I'm trying to add a custom analyzer which will lowercase terms, but preserve them as the whole term, so eg
ABC123
becomes the single termabc123
However, if I search for
ABC123
I would expect it to be converted to a search forabc123
, and this isn't happening. If I search forabc123
then I get the correct results:The text was updated successfully, but these errors were encountered: