# Mapping change on upgrade to 5.2.2

**URL:** <https://discuss.elastic.co/t/mapping-change-on-upgrade-to-5-2-2/82622>\
**Category:** Elasticsearch\
**Created:** [April 17, 2017, 7:45pm UTC](https://discuss.elastic.co/t/mapping-change-on-upgrade-to-5-2-2/82622 "2017-04-17T19:45:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vin01](https://avatars.discourse-cdn.com/v4/letter/v/bc8723/32.png) [@vin01](https://discuss.elastic.co/u/vin01)\
**Post date:** [April 17, 2017, 7:45pm UTC](https://discuss.elastic.co/t/mapping-change-on-upgrade-to-5-2-2/82622/1 "2017-04-17T19:45:57Z")

</div>

The mapping for fields in ES 2.3.3 was like:

```
fieldname {
type: "string",
fields: {
raw: {
type: "string",
index: "not_analyzed"
}
}
}

```

Now after upgrade to 5.2.2, it has become like:

```
fieldname: {
type: "string",
fields: {
raw: {
type: "string",
index: "not_analyzed",
fielddata: false
}
}
}

```

fielddata:false doesn't seem to be a valid mapping. Valid mapping to disable fielddata would be "fielddata":{"format":"disabled"}.

I do see fielddata being used for fieldname.raw, however reason for that could be the ordinals' memory consumption which is shown in fielddata ([https://github.com/elastic/elasticsearch/issues/17472](https://github.com/elastic/elasticsearch/issues/17472)).

I have been wondering if there is any specific reason for this change in mapping on upgrade, and what can be the possible implications on performance (if any).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 15, 2017, 7:58pm UTC](https://discuss.elastic.co/t/mapping-change-on-upgrade-to-5-2-2/82622/2 "2017-05-15T19:58:42Z")

</div>

Closed on May 15, 2017, 7:58pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.