# Parsing Exception on Mapped Type Object Enabled False **URL:** \ **Category:** Elasticsearch\ **Created:** [April 17, 2024, 2:15pm UTC](https://discuss.elastic.co/t/parsing-exception-on-mapped-type-object-enabled-false/357633 "2024-04-17T14:15:42Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![maxfriz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/maxfriz/32/123814_2.png) [@maxfriz](https://discuss.elastic.co/u/maxfriz)\ **Post date:** [April 17, 2024, 2:15pm UTC](https://discuss.elastic.co/t/parsing-exception-on-mapped-type-object-enabled-false/357633/1 "2024-04-17T14:15:42Z")
One of our fields in our field mapping is mapped as type object with enabled set to false. It is our understanding this is stored in \_source, but not parsed or indexed. ```auto "payload": { "type": "object", "enabled": false }, ``` We have been successfully utilizing this mapping for some time now with 500K records indexed. All of a sudden, we are getting a mapper\_parsing\_exception referencing a field in the stored object where the parser is trying to parse a date and there is a text value. If we were indexing this field and we had a field mapped as date, this parsing exception would make sense. Otherwise, why all of a sudden is any data in this field being parsed? I just want to confirm my understanding "we should be able to put any JSON object we want ... even completely different types of JSON objects in a field mapped as type object and when enabled is set to false, there should be no parsing or indexing at all". Is this correct? ---
**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, 2024, 2:15pm UTC](https://discuss.elastic.co/t/parsing-exception-on-mapped-type-object-enabled-false/357633/2 "2024-05-15T14:15:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.