# Mapping definition for ... has unsupported parameters: \[index : no\]
**URL:** https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911
**Category:** Elasticsearch
**Created:** [March 19, 2016, 9:48pm UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911 "2016-03-19T21:48:04Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@jsbloonix](https://discuss.elastic.co/u/jsbloonix)
#### Post date: [March 19, 2016, 9:48pm UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/1 "2016-03-19T21:48:04Z")
Hi together,
I'm trying to update from ES 1.7 to ES 2.1 and got some errors.
"Mapping definition for [data] has unsupported parameters: [index : no]".
> "properties": {
> "data" : {
> "type" : "object",
> "index" : "no"
> }
Is "index : no" not valid any more? The documentation lists it still as valid: [Mapping | Elasticsearch: The Definitive Guide [2.x] | Elastic](https://www.elastic.co/guide/en/elasticsearch/guide/current/mapping-intro.html)
Under "data" a JSON object is stored and I want that Elasticsearch ignores the data completly.
Regards
Jonny
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 20, 2016, 5:00am UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/2 "2016-03-20T05:00:23Z")
It does not make sense on an object.
An actually I think it was simply ignored in previous versions.
But from 2.0 the check is more strict .
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [March 20, 2016, 5:02am UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/3 "2016-03-20T05:02:44Z")
I think you want to use enabled here.
See [https://www.elastic.co/guide/en/elasticsearch/reference/2.2/object.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.2/object.html)
---
### Author:  [@jsbloonix](https://discuss.elastic.co/u/jsbloonix)
#### Post date: [March 20, 2016, 1:41pm UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/4 "2016-03-20T13:41:36Z")
Ok, I understand, thank you. 🙂
But why I have to reindex all indexes for a feature that were ignored in past releases? That makes no sense to me. If the feature were ignored and had no effect then it would be much easier if Elasticsearch just delete it from the mapping and the current data instead to force me to reindex terabytes of data.
Is there a hope?
---
### Author:  [@jsbloonix](https://discuss.elastic.co/u/jsbloonix)
#### Post date: [March 20, 2016, 1:51pm UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/5 "2016-03-20T13:51:33Z")
Yes, great, the option "enabled" is that what I need. The JSON data are stored, but not indexed. That is what I expected with "index : no".
Now the question: is it really necessary to reindex all indexes for an option that were ignored and had no effect in past releases of Elasticsarch?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:06pm UTC](https://discuss.elastic.co/t/mapping-definition-for-has-unsupported-parameters-index-no/44911/6 "2017-07-05T23:06:45Z")