So Slavag seems to have something strange on its side as he said that he got for
step 4 :
{
"test" : {
"type" : {
"properties" : {
"test" : {
"type" : "string"
}
}
}
}
}
HTH,
David.
Le 13 décembre 2011 à 23:10, Shay Banon kimchy@gmail.com a écrit :
I am not really sure..., I don't see where the problem is. Can someone else
try and recreate this problem, or verify that its not happening? I will
repeat the recreation:
Use a fresh elasticsearch 0.18.5 installation.
Place a file called default-mapping.json under config with the following
content:
Hi David,
Can you please run this curl -XGET localhost:9200/test/_search?pretty=true
-d '
{
"query" : {
"term" : { "test" : "value" }
}
}
'
What is the result ?
I get a single hit without source :
{
"took":0,
"timed_out":false,
"_shards":{
"total":5,
"successful":5,
"failed":0
},
"hits":{
"total":1,
"max_score":0.30685282,
"hits":[{
"_index":"test",
"_type":"type",
"_id":"1",
"_score":0.30685282
}
]
}
}
Hi David,
Can you please run this curl -XGET localhost:9200/test/_search?pretty=true
-d '
{
"query" : {
"term" : { "test" : "value" }
}
}
'
What is the result ?
--
David Pilato http://dev.david.pilato.fr/
Twitter : @dadoonet
I test it under windows using mobz inteface. That's perhaps why GET produces
nothing for me...
BTW, I remember having some troubles some months ago with mappings in conf dir.
Let me tell something that not answer directly to your concern. It could be a
better idea to send mapping to an ES node instead of having to copy on each node
a conf file.
BTW, are you really sure that your 0.18.5 is a fresh one ?
Do you have some globals var in your system (what printenv produces ?) ?
Hi David,
Thank for quick response , per your question - yes this is fresh 18.5 -
just unpacked it and put the mapping in the config.
Can you describe a little bit more the sending mapping to an ES node ?
As for global vars in the system I don't see any special, but is there some
global vars that has effect on the ES ?
is the unix script to push mapping files to a node (localhost:9200)
./createMapping mymapping
It sends the mymapping.json file to ES. Then ES spread the mapping to each
nodes.
Is a sample mapping JSON file
Not sure that is what you are after but may help...
About ES VARS, I was only thinking about ES_JAVA_OPTS or JAVA_OPTS in which you
can have defined a -Des.path.data or -Des.path.conf or something like that.
Hi David,
Thank for quick response , per your question - yes this is fresh 18.5 -
just unpacked it and put the mapping in the config.
Can you describe a little bit more the sending mapping to an ES node ?
As for global vars in the system I don't see any special, but is there some
global vars that has effect on the ES ?
David, Thank You a lot.
Looking on the script and it seems that i need it of each index, now when
my application is multi-tanant application and new index are coming as new
customer is join and even more the new index types are also can come pretty
often. So it means that I need to put mapping for every new tenant (new
index) / for every new index type.
Do you see any other solution to my case - btw, the mapping that I need for
all index type and for all tenants ( at least the the mandatory fields) are
very few : some date, id of data and user account. Those are 3 fields that
I need to store and not analyze and I have to not store _source.
David, Thank You a lot.
Looking on the script and it seems that i need it of each index, now when
my application is multi-tanant application and new index are coming as new
customer is join and even more the new index types are also can come pretty
often. So it means that I need to put mapping for every new tenant (new
index) / for every new index type.
Do you see any other solution to my case - btw, the mapping that I need
for all index type and for all tenants ( at least the the mandatory fields)
are very few : some date, id of data and user account. Those are 3 fields
that I need to store and not analyze and I have to not store _source.
Operating system does not matter. The only two reasons that I can think can
cause it is that you are not using the config location you think you are
using, or there is another node started that acts as the master with a
different configuration.
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.