Hi Shay,
Can we change from dynamic:false to dynamic:true in case of custom mapping?
Also it would be useful to know what all can we change in the mapping
which doesn't require the re-indexing of the older data?
Thanks in advance..!!
On Wednesday, May 30, 2012 1:55:20 AM UTC-7, kimchy wrote:
You can't change the index mapping setting of a field.
On Sun, May 27, 2012 at 5:45 PM, feridcelik <ferid...@gmail.com<javascript:>
wrote:
I got the same issue with java api 0.19.4, and also with 0.19.3.
Putting new mappings work, but cant update. Code doesnt throw any
exception
or something.PutMappingRequestBuilder rq =
client.admin().indices().preparePutMapping("someIndex");
rq.setType("xxxx").setSource(TYPE_MAPPING_SOURCE);
rq.setIgnoreConflicts(true);initial mapping source(TYPE_MAPPING_SOURCE) is something like this:
{
"xxxx" : {
"properties" : {
"someText" : {
"type" : "string",
"index" : "not_analyzed"
}
}
}
}and im trying to update it to:
{
"xxxx" : {
"properties" : {
"someText" : {
"type" : "string",
"index" : "no"
}
}
}
}I also tried closing index before trying to update, but it doesnt work
too.When i set ignoreConflicts,
rq.setIgnoreConflicts(false);api throws an exception
org.elasticsearch.index.mapper.MergeMappingException: Merge failed with
failures {[mapper [someText] has different index values]}Ferid Gürbüz
--
View this message in context:
http://elasticsearch-users.115913.n3.nabble.com/Update-mapping-tp3957288p4018140.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.
--