I know that case insensitive searching has been covered in a couple
other threads but I feel like this question is a little different.
We have two fields that need to be case insensitive when we search for
them as they need to be completely unique across the application, say
fields "username" and "emailAddress".
Setting the "username" field to be analyzed solves the issue for it as
we only want alphanumeric characters to comprise the username (I feel
like we would be in trouble though if we had to set it as "analyzed").
But if we set "emailAddress" to be analyzed will the default analyzer
split it based on the "@" symbol (therefore returning anything that
matches after the @ symbol)?
Is there a configuration (or query parameters) to have a field set to
"not_analyzed" but still search case insensitively?
I know that case insensitive searching has been covered in a couple
other threads but I feel like this question is a little different.
We have two fields that need to be case insensitive when we search for
them as they need to be completely unique across the application, say
fields "username" and "emailAddress".
Setting the "username" field to be analyzed solves the issue for it as
we only want alphanumeric characters to comprise the username (I feel
like we would be in trouble though if we had to set it as "analyzed").
But if we set "emailAddress" to be analyzed will the default analyzer
split it based on the "@" symbol (therefore returning anything that
matches after the @ symbol)?
Is there a configuration (or query parameters) to have a field set to
"not_analyzed" but still search case insensitively?
--
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.
--
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.
--
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.
Properties files are a pain when it comes to array definitions, before I
suggest the format, can you simply use yaml/json and load elasticsearch with
it?
--
Web Announcements Limited is a company registered in England and Wales,
with company number 05608868, with registered address at 10 Arvon Road,
London, N5 1PR.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the server
properties from a properties file because that is what Spring supports.
Is this array format you allude to able to be loaded using Java's property
file support?
Properties files are a pain when it comes to array definitions, before I
suggest the format, can you simply use yaml/json and load elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England and
Wales,
with company number 05608868, with registered address at 10 Arvon
Road,
London, N5 1PR.
Let me explain what I allude you are able to do (though not collude, which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your decision
to use properties files as a configuration format or not, spring does not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an external
(classpath, or other) configuration file using json or yaml. Custom ${...}
values will automatically be replaced with system properties. Check the
SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an array. Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the server
properties from a properties file because that is what Spring supports.
Is this array format you allude to able to be loaded using Java's property
file support?
Properties files are a pain when it comes to array definitions, before I
suggest the format, can you simply use yaml/json and load elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England and
Wales,
with company number 05608868, with registered address at 10 Arvon
Road,
London, N5 1PR.
Let me explain what I allude you are able to do (though not collude, which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your decision
to use properties files as a configuration format or not, spring does not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an
external (classpath, or other) configuration file using json or yaml. Custom
${...} values will automatically be replaced with system properties. Check
the SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an array. Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the
server properties from a properties file because that is what Spring
supports.
Is this array format you allude to able to be loaded using Java's property
file support?
Properties files are a pain when it comes to array definitions, before I
suggest the format, can you simply use yaml/json and load elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England and
Wales,
with company number 05608868, with registered address at 10 Arvon
Road,
London, N5 1PR.
But I'm still getting some errors (i.e. "Analyzer [lowercase_keyword]
not found") when I associate a file to "analyzer":"lowercase_keyword"
in the mapping.
Anything I'm missing here?
Let me explain what I allude you are able to do (though not collude, which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your decision
to use properties files as a configuration format or not, spring does not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an
external (classpath, or other) configuration file using json or yaml. Custom
${...} values will automatically be replaced with system properties. Check
the SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an array. Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the
server properties from a properties file because that is what Spring
supports.
Is this array format you allude to able to be loaded using Java's property
file support?
Properties files are a pain when it comes to array definitions, before I
suggest the format, can you simply use yaml/json and load elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England and
Wales,
with company number 05608868, with registered address at 10 Arvon
Road,
London, N5 1PR.
This settings seem ok. Can you recreate this with fresh elasticsearch
install, rename elasticsearch.yml to elasticsearch.properties, place the
relevant properties and gist a curl recreation?
But I'm still getting some errors (i.e. "Analyzer [lowercase_keyword]
not found") when I associate a file to "analyzer":"lowercase_keyword"
in the mapping.
Anything I'm missing here?
Let me explain what I allude you are able to do (though not collude,
which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your
decision
to use properties files as a configuration format or not, spring does
not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an
external (classpath, or other) configuration file using json or yaml.
Custom
${...} values will automatically be replaced with system properties.
Check
the SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an array.
Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the
server properties from a properties file because that is what Spring
supports.
Is this array format you allude to able to be loaded using Java's
property
file support?
Properties files are a pain when it comes to array definitions,
before I
suggest the format, can you simply use yaml/json and load
elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England
and
Wales,
with company number 05608868, with registered address at 10
Arvon
Road,
London, N5 1PR.
The error was caused because we added the custom analyzer config to our ES
server config only. The ES clients did not have this information and were
the cause of the exception.
This settings seem ok. Can you recreate this with fresh elasticsearch
install, rename elasticsearch.yml to elasticsearch.properties, place the
relevant properties and gist a curl recreation?
But I'm still getting some errors (i.e. "Analyzer [lowercase_keyword]
not found") when I associate a file to "analyzer":"lowercase_keyword"
in the mapping.
Anything I'm missing here?
Let me explain what I allude you are able to do (though not collude,
which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your
decision
to use properties files as a configuration format or not, spring does
not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an
external (classpath, or other) configuration file using json or yaml.
Custom
${...} values will automatically be replaced with system properties.
Check
the SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an array.
Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the
server properties from a properties file because that is what Spring
supports.
Is this array format you allude to able to be loaded using Java's
property
file support?
Properties files are a pain when it comes to array definitions,
before I
suggest the format, can you simply use yaml/json and load
elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England
and
Wales,
with company number 05608868, with registered address at 10
Arvon
Road,
London, N5 1PR.
You can always provide the analyzes as part of the index configuration when
you create an index (And not part of the node configuration), then it will
propagate through the nodes.
The error was caused because we added the custom analyzer config to our ES
server config only. The ES clients did not have this information and were
the cause of the exception.
This settings seem ok. Can you recreate this with fresh elasticsearch
install, rename elasticsearch.yml to elasticsearch.properties, place the
relevant properties and gist a curl recreation?
But I'm still getting some errors (i.e. "Analyzer [lowercase_keyword]
not found") when I associate a file to "analyzer":"lowercase_keyword"
in the mapping.
Anything I'm missing here?
Let me explain what I allude you are able to do (though not collude,
which
seems to be making twitter noise lately...):
First, Spring does not imply using just properties files. Its your
decision
to use properties files as a configuration format or not, spring does
not
enforce you to use it.
You can easily configure elasticsearch to load the settings from an
external (classpath, or other) configuration file using json or yaml.
Custom
${...} values will automatically be replaced with system properties.
Check
the SettingsLoader and different implementations.
If you do want to use properties files, then suffixing
the appropriate setting with .0, .1 and so on will imply its an
array. Off,
sorry, allude its an array.
Hi shay,
My ES instance is bootstrapped and configured via spring. I load the
server properties from a properties file because that is what Spring
supports.
Is this array format you allude to able to be loaded using Java's
property
file support?
Properties files are a pain when it comes to array definitions,
before I
suggest the format, can you simply use yaml/json and load
elasticsearch
with
it?
--
Web Announcements Limited is a company registered in England
and
Wales,
with company number 05608868, with registered address at 10
Arvon
Road,
London, N5 1PR.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.