search

elastic / elasticsearch-migration

This plugin will help you to check whether you can upgrade directly to the next major version of Elasticsearch, or whether you need to make changes to your data and cluster before doing so.
290 stars 32 forks source link

Strange mapping conflict found #40

Closed slavag closed 8 years ago

slavag commented 9 years ago

I ran migration checker to see if I can move from ES 1.7.1 to 2.0 and got many mapping conflicts, one of them is that I have within same index 2 different types each one of them has same field : account and it's mapping is (both fields has exactly same mapping):

type : string _index : notanalyzed store : no _docvalues : true

Here the exact mapping (Java) :

Type A: .... .startObject("account") .field("type", "string") .field("index", "not_analyzed") .field("store", "no") .field("doc_values","true") .endObject() ....

Type B: .... .startObject("account") .field("type", "string") .field("index", "not_analyzed") .field("store", "no") .field("doc_values","true") .endObject() .... They exactly the same, so, I don't see any conflict between two of them, but maybe I'm missing something. Any advise ? Thanks

clintongormley commented 9 years ago

Hi @slavag

Could you upload the result of:

GET my_index/_mapping

thanks

clintongormley commented 8 years ago

No more feedback. Closing