thank you for your fast reply.
this actually happened with 1.4.0Beta1 so I am not sure if it's the same
issue.
the mapping was changed by a script and the error not caught with the
mapping value added, the trace of the first occurence is
[DEBUG][action.admin.indices.mapping.put] [Dorma] failed to put mappings on
indices [[INDEX]], type [TYPE]
org.elasticsearch.index.mapper.MergeMappingException: Merge failed with
failures {[mapper [_all] has different store values, mapper [_all] has
different store_term_vector values, mapper [_all] has different
store_term_vector_offsets values, mapper [_all] has different
store_term_vector_positions values]}
at
org.elasticsearch.cluster.metadata.MetaDataMappingService$4.execute(MetaDataMappingService.java:511)
at
org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:329)
at
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:153)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Am Freitag, 7. November 2014 12:12:29 UTC+1 schrieb Michael McCandless:
>
> Hmm this is likely due to
> https://github.com/elasticsearch/elasticsearch/pull/7377
> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Felasticsearch%2Felasticsearch%2Fpull%2F7377&sa=D&sntz=1&usg=AFQjCNEQgpIcl_fREseYc_pd1kEupGv32A>
>
> (fixed in 1.4.0Beta1) which was done to prevent conflicting mapping changes
> to the _all field.
>
> What change are you trying to make, that hits this error? Is there a
> stack trace?
>
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Fri, Nov 7, 2014 at 5:31 AM, <[email protected] <javascript:>> wrote:
>
>> Hi,
>>
>> with 1.40Beta1 all of a sudden we can not change the mapping on existing
>> -not all- types in our index anymore.
>>
>>
>> *mapper [_all] has different store values, *
>> *mapper [_all] has different store_term_vector values, *
>> *mapper [_all] has different store_term_vector_offsets values, *
>> *mapper [_all] has different store_term_vector_positions values*
>>
>>
>> This happened with all existing types in the index.
>>
>> Adding new types and changing the mapping is possible.
>>
>> Upgrading to 1.40 and restoring a snapshot did not solve this problem.
>>
>> Setting store* to false results in the same error message, disabling an
>> enabled _all field is also not possible.
>>
>> Did this ever happened to somebody else?
>>
>> --
>> 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] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/dfc57323-8293-4bcc-9355-10e7a684264b%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/dfc57323-8293-4bcc-9355-10e7a684264b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
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/37ffa4ad-0762-4c5d-aa94-b9add636f8d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
