Hi,
We already have a type in our system, *YsFact*. Now I needed to
add a new field in this type, *username*. And username has following
mapping.
*"username":{"type":"string","index":"not_analyzed"}*
We have a script in the system, that executes the mappings automatically.
and in the execution of mapping, I am getting the following errors.
YsFact :: MergeMappingException[Merge failed with failures {[mapper
[username] has different index values, mapper [username] has different
`norms.enabled` values, mapper [username] has different tokenize values,
mapper [username] has different index_analyzer]}]
Although, We have not added anything against username in the YsFact type.
So I do not think so that Elasticsearch should have created some default
mappings on it as no data indexed against this field. This was the response
for the first time,we introduced this field in mappings.
One thing, I want to notify is that, we have username fields in other types
which has data against the username. Can it conflict the YsFact ??
Also Our Production Elasticsearch server consists of 3 nodes and 2
replicas. Can something related to distribution there ?
Does anyone have any idea what happend over here?
Thanks in advance for all kind of details on it.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7f5d6215-6388-489d-9810-9cc2fc0972f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
