# Mapping rejected w/ type: object, index: no
**URL:** https://discuss.elastic.co/t/mapping-rejected-w-type-object-index-no/43434
**Category:** Elasticsearch
**Created:** [March 3, 2016, 8:02pm UTC](https://discuss.elastic.co/t/mapping-rejected-w-type-object-index-no/43434 "2016-03-03T20:02:03Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@mpowers](https://discuss.elastic.co/u/mpowers)
#### Post date: [March 3, 2016, 8:02pm UTC](https://discuss.elastic.co/t/mapping-rejected-w-type-object-index-no/43434/1 "2016-03-03T20:02:03Z")
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](https://www.elastic.co/guide/en/elasticsearch/reference/current/object.html) 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?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:11pm UTC](https://discuss.elastic.co/t/mapping-rejected-w-type-object-index-no/43434/2 "2017-07-05T23:11:29Z")