On Fri, Nov 7, 2014 at 6:41 AM, <[email protected]> wrote:
> thank you for your fast reply.
>
> this actually happened with 1.4.0Beta1 so I am not sure if it's the same
> issue.
>
Sorry, what I mean is that this issue, which adds checking for mapping
conflicts in the _all field and was fixed in 1.4.0Beta1, causes the problem
you're seeing.
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)
>
Hmm, is that script trying to change the mapping for the _all field?
Mike McCandless
http://blog.mikemccandless.com
--
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/CAD7smRfYAGaxS4xKfTLoWj0ZhwgzMpzETGTbhvL%3DX9vad4TgqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
