Hello everyone,
A problem that I'm trying to handler now it's how to update an existing
mapping after its creation (not adding new fields, but more like to
delete/modify existing ones).
Apparently, read from lots of existing posts, it's not possible unless we
reindex the whole data again.
Since we have the possibility of setting "index":"no" to a property during
the creation of a mapping, so that this property won't be searchable.
So I tested the following scripts.
I created a mapping for a type :
PUT test/mytype/_mapping
{
"mytype" : {
"properties" : {
"id": {"type" : "string"},
"name": {"type" : "string"},
"age": {"type" : "integer"},
"message" : {"type" : "string"}
}
}
}
Then I closed the index, and try to modify the mapping by the following
script
PUT test/mytype/_mapping?ignore_conflicts=true
{
"mytype" : {
"properties" : {
"id": {"type" : "string"},
"name": {"type" : "string"},
"age": {"type" : "integer"},
"message" : {"type" : "string","index": "no"}
}
}
}
Since I choose the option to ignore_conflicts=true, no exception is
returned, but in the same time, nothing happened neither on the mapping.
My question is :
Is there any solution, without reindex the whole data, to disable the
search on some existing properties after creation and insertion of a type?
Thank you very much.
Jac
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a0be22b9-ea77-4801-8251-94ca53389e90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.