I noticed that even if I set { "index": "not_analyzed" } for certain types of fields, like for instance integer, it apparently ignores, because when I fetch the mapping for the given index/type, such attribute doesn't come together with the given field.
That is obvious, given analyzing integer fields doesn't make sense at all.
So my question is: should I consider only "string" fields to bring such "index" attribute when retrieving mappings from the server? So, considering the existing core types, should I consider the types integer/long, float/double and boolean as types where the "index" attribute doesn't apply to?