HI All
I am having a very weird problem with fields that are configured as
not_analysed for some reason the value is being tokenised even when i have
the field configured as not_analyzed i am sure i am missing something very
simple i just cant seem to figure out what,this is how my mapping looks like
"settings": {
"number_of_shards": 5,
"number_of_replicas": 2
},
"mappings": {
"story": {
"properties": {
"section": {
"type": "string",
"index": "not_analyzed"
}
}
}
}
curl -XPOST localhost:9200/my_index -d @mapping.json
when i index data
curl -XPOST localhost:9200/my_index/story -d '{
"section": "fast-forward"
}'
and i look at http://localhost:9200/my_index/_termlist
i see it as individual terms.i know i am missing something simple cant
figure out what it is,somebody please help
HI All
I am having a very weird problem with fields that are configured as not_analysed for some reason the value is being tokenised even when i have the field configured as not_analyzed i am sure i am missing something very simple i just cant seem to figure out what,this is how my mapping looks like
"settings": {
"number_of_shards": 5,
"number_of_replicas": 2
},
"mappings": {
"story": {
"properties": {
"section": {
"type": "string",
"index": "not_analyzed"
}
}
}
}
curl -XPOST localhost:9200/my_index -d @mapping.json
when i index data
curl -XPOST localhost:9200/my_index/story -d '{
"section": "fast-forward"
}'
and i look at http://localhost:9200/my_index/_termlist
i see it as individual terms.i know i am missing something simple cant figure out what it is,somebody please help
Thanks David,i solved this problem by adding
curl -XPUT localhost:9200/my_index -d '@mapping.json'
replace POST with PUT and added single-quote on the file name and
everything is working as expected,its bizarre but i guess i wasnt doing
this right before
Kalyan
On Tuesday, December 23, 2014 7:34:07 PM UTC-8, David Pilato wrote:
You should check that your mapping has been applied.
GET my_index/store/_mapping
David
Le 24 déc. 2014 à 00:35, Kalyan Srinivas <kalyan...@gmail.com
<javascript:>> a écrit :
HI All
I am having a very weird problem with fields that are configured as
not_analysed for some reason the value is being tokenised even when i have
the field configured as not_analyzed i am sure i am missing something very
simple i just cant seem to figure out what,this is how my mapping looks like
"settings": {
"number_of_shards": 5,
"number_of_replicas": 2
},
"mappings": {
"story": {
"properties": {
"section": {
"type": "string",
"index": "not_analyzed"
}
}
}
}
curl -XPOST localhost:9200/my_index -d @mapping.json
when i index data
curl -XPOST localhost:9200/my_index/story -d '{
"section": "fast-forward"
}'
and i look at http://localhost:9200/my_index/_termlist
i see it as individual terms.i know i am missing something simple cant
figure out what it is,somebody please help
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.