We are currently running version 1.7.5 in production. I am researching moving to 2.2.0. Our current mappings have several fields with "type": "object" and "index": "no". I am getting this error when deploying mappings onto a 2.2.0 cluster: {"error":{"root_cause":[{"type":"mapper_parsing_exception","reason":"Mapping definition for [associations_lookup] has unsupported parameters: [index : no]"}],"type":"mapper_parsing_exception","reason":"Mapping definition for [associations_lookup] has unsupported parameters: [index : no]"},"status":400}. I have found some documentation that suggests that 2.2.0 no longer supports "index" on object-type fields, but instead has an "enabled" option.
Is setting "enabled": "false" exactly equivalent to "index": "no" for object-type fields now?