Different mappings are wrong about monstache HOT 7 CLOSED

Now I have to land the ES version to 5.x

from monstache.

Perhaps the best solution to that would be to use JavaScript to coerce the no field into a number array type. So, you would need to detect form 2 or form 3 and use code to transform to form 1. Delete the index and rerun monstache to reindex the data with same type.

Or if you don’t need to search this field you could simply set up a mapping in ES such that the no field is not indexed.

from monstache.

Example to disable a field if you choose to not transform in JavaScript.

https://www.elastic.co/guide/en/elasticsearch/reference/current/enabled.html

from monstache.

thx！
If I keep all，The best way should be。。。。。？
no.length>2
no=2
no.no1=1
Suppose all want to query

Is not only using the low version 5.x？

from monstache.

I do not quite understand why it（es 6） does not have a better solution, only to delete the index

from monstache.

To my knowledge there's no difference between ES 5 and 6 with regards to this. When using dynamic mapping the first document indexed determines the field types and subsequent documents must conform to that type.

Once the index is created, you cannot change the type mapping of existing fields in ES 5 or 6, only reindex the into another index or delete the index and recreate. Are you saying you can successfully index a field with multiple data types in ES 5?

The javascript I was thinking of would be something like

module.exports = function(doc) {
    if (doc.no) {
      if (!Array.isArray(doc.no)) {
         // only if ordering of values not important
         doc.no = _.values(doc.no);
      }
    }
    return doc;
}

from monstache.

I think I should understand. Thank you very much!

from monstache.