What I'm trying to do is to get data by filtering term with exact
matching. I have ES 1.3.2 and I cannot do mapping, as attributes are
dynamic (different users has different attributes). My data:
David Pilato proposed that "index has indexed probably not and approved"
and that there is no exact matching to "not approved". I tried to search
for word "not" and it works
Just to be clear, actually I don't need any analyzer on filters
On Tuesday, October 7, 2014 12:57:32 PM UTC+3, Vladimir Krylov wrote:
What I'm trying to do is to get data by filtering term with exact
matching. I have ES 1.3.2 and I cannot do mapping, as attributes are
dynamic (different users has different attributes). My data:
David Pilato proposed that "index has indexed probably not and approved"
and that there is no exact matching to "not approved". I tried to search
for word "not" and it works
I tried to set custom default analyzer
curl -XPUT 'host:9200/reports' -d '
{
"settings":{
"analysis": {
"analyzer": {
"default":{
"type": "pattern",
"pattern":"_________" // I know that cannot get
this splitter
}
}
}
}
}'
curl 'http://host:9200/reports/_analyze?pretty=1&field=filter__approval' -d
'not approved' # returns full string as one token
curl 'http://host:9200/reports/_analyze?pretty=1' -d 'foo,bar baz ASD: "
fdfd "'# returns full string as one token
Seems to be working. Is there better solution?
On Tuesday, October 7, 2014 12:57:32 PM UTC+3, Vladimir Krylov wrote:
What I'm trying to do is to get data by filtering term with exact
matching. I have ES 1.3.2 and I cannot do mapping, as attributes are
dynamic (different users has different attributes). My data:
David Pilato proposed that "index has indexed probably not and approved"
and that there is no exact matching to "not approved". I tried to search
for word "not" and it works
The field do not need a custom analyzer, they just need to be simply marked
as non_analyzed.
You can setup a dynamic template that states any new field should be non
analyzed.
You can still hardcode the mapping for specific fields.
Cheers,
Ivan
On Oct 7, 2014 2:57 AM, "Vladimir Krylov" s6numid@gmail.com wrote:
What I'm trying to do is to get data by filtering term with exact
matching. I have ES 1.3.2 and I cannot do mapping, as attributes are
dynamic (different users has different attributes). My data:
David Pilato proposed that "index has indexed probably not and approved"
and that there is no exact matching to "not approved". I tried to search
for word "not" and it works
You can still hardcode the mapping for specific fields.
Cheers,
Ivan
On Oct 7, 2014 2:57 AM, "Vladimir Krylov" <s6n...@gmail.com <javascript:>>
wrote:
What I'm trying to do is to get data by filtering term with exact
matching. I have ES 1.3.2 and I cannot do mapping, as attributes are
dynamic (different users has different attributes). My data:
David Pilato proposed that "index has indexed probably not and approved"
and that there is no exact matching to "not approved". I tried to search
for word "not" and it works
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.