You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearch version (bin/elasticsearch --version): 5.5.0
Plugins installed: []
JVM version (java -version):
OS version (uname -a if on a Unix-like system): Ubunutu 16.0
Description of the problem including expected versus actual behavior:
I found that when we run the search query for string which has Uppercase and Lowercase characters, it failed to return the correct records. Anyone faced the problem.
So, changing the string to lowercase before search solved the problem for my system.
Can that be changed in the package, so that its easier for other users.
Spent a long time solve problem caused by this.
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered:
You're using a term query which finds documents that contain the exact term specified in the inverted index.
I am closing this as we use Github for bug reports and feature requests. Please ask questions on https://discuss.elastic.co where we can give you a better support.
The exact value that is stored in field is the word that starts with the uppercase "Gobinda".
whereas the search term only works with the lowercase not while putting the word with uppercase.
Describe the feature:
Elasticsearch version (
bin/elasticsearch --version
): 5.5.0Plugins installed: []
JVM version (
java -version
):OS version (
uname -a
if on a Unix-like system): Ubunutu 16.0Description of the problem including expected versus actual behavior:
I found that when we run the search query for string which has Uppercase and Lowercase characters, it failed to return the correct records. Anyone faced the problem.
So, changing the string to lowercase before search solved the problem for my system.
Can that be changed in the package, so that its easier for other users.
Spent a long time solve problem caused by this.
Steps to reproduce:
Please include a minimal but complete recreation of the problem, including
(e.g.) index creation, mappings, settings, query etc. The easier you make for
us to reproduce it, the more likely that somebody will take the time to look at it.
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: