# Jackson error parsing JSON **URL:** \ **Category:** Elasticsearch\ **Created:** [November 30, 2011, 3:53pm UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029 "2011-11-30T15:53:56Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![James\_Cook\_3](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@James\_Cook\_3](https://discuss.elastic.co/u/James_Cook_3)\ **Post date:** [November 30, 2011, 3:53pm UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029/1 "2011-11-30T15:53:56Z")
I've just encountered a regression bug, and I'm not sure if it is related to a recent change in elasticsearch. I am attempting to index the following JSON document. [ { "dataType": "posts", "spam": 0, "likes": 0, "views": 0, "active": true, "dateCreated": "2011-11-30T15:43:48Z", "type": "comment", "creator": { "\_id": "9471705a52bb429aa3931c682f4a53c7", "username": "malayed1", "thumbnail": { "idSource": "profiles-0000-0000-0000-000000000001", "idCrop": "profiles-0000-0000-0000-000000000001" }, "fullName": "Mohamed Al Ayed", "dataType": "profiles" }, "title": "", "message": " Great idea for a new company. ", "likedBy": [], "lastModifiedDate": "2011-11-30T15:43:48Z", "threadId": "f49d43ac71774c5aa08f96a66b257ca0", "parentId": "7669edcfac4c4c75bfc93f698ecd3292", "\_id": "f49d43ac71774c5aa08f96a66b257ca0" } ] It is valid JSON, but ES is failing to parse it and throwing an exception. org.elasticsearch.index.mapper.MapperParsingException: Failed to parse [active] at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:308) at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue(ObjectMapper.java:577) at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:443) at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:468) at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:409) at org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:302) at org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:181) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:487) at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:400) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: org.elasticsearch.common.jackson.JsonParseException: Current token (VALUE\_TRUE) not numeric, can not use numeric value accessors at [Source: [B@344026c1; line: 1, column: 63] ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 30, 2011, 4:19pm UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029/2 "2011-11-30T16:19:53Z")
Can you post a recreation? It might need the mappings associated with it. On Wed, Nov 30, 2011 at 5:53 PM, James Cook [jcook@pykl.com](mailto:jcook@pykl.com) wrote: > I've just encountered a regression bug, and I'm not sure if it is related > to a recent change in elasticsearch. > > I am attempting to index the following JSON document. > > [ > { > "dataType": "posts", > "spam": 0, > "likes": 0, > "views": 0, > "active": true, > "dateCreated": "2011-11-30T15:43:48Z", > "type": "comment", > "creator": { > "\_id": "9471705a52bb429aa3931c682f4a53c7", > "username": "malayed1", > "thumbnail": { > "idSource": "profiles-0000-0000-0000-000000000001", > "idCrop": "profiles-0000-0000-0000-000000000001" > }, > "fullName": "Mohamed Al Ayed", > "dataType": "profiles" > }, > "title": "", > "message": " > > Great idea for a new company. > > ", > "likedBy": , > "lastModifiedDate": "2011-11-30T15:43:48Z", > "threadId": "f49d43ac71774c5aa08f96a66b257ca0", > "parentId": "7669edcfac4c4c75bfc93f698ecd3292", > "\_id": "f49d43ac71774c5aa08f96a66b257ca0" > } > ] > > It is valid JSON, but ES is failing to parse it and throwing an exception. > > org.elasticsearch.index.mapper.MapperParsingException: Failed to parse > [active] > at > org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:308) > at > org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue(ObjectMapper.java:577) > at > org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:443) > at > org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:468) > at > org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:409) > at > org.elasticsearch.index.shard.service.InternalIndexShard.prepareIndex(InternalIndexShard.java:302) > at > org.elasticsearch.action.index.TransportIndexAction.shardOperationOnPrimary(TransportIndexAction.java:181) > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:487) > at > org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:400) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > Caused by: org.elasticsearch.common.jackson.JsonParseException: Current > token (VALUE\_TRUE) not numeric, can not use numeric value accessors > at [Source: [B@344026c1; line: 1, column: 63] ---
**Author:** ![James\_Cook\_3](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@James\_Cook\_3](https://discuss.elastic.co/u/James_Cook_3)\ **Post date:** [November 30, 2011, 5:56pm UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029/3 "2011-11-30T17:56:01Z")
Yes, mapping was wrong. I didn't realize it referenced mapping files. Thanks! ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [November 30, 2011, 6:00pm UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029/4 "2011-11-30T18:00:14Z")
Would still be great to get a simple recreation, that error message is cryptic..., should be fixed. On Wed, Nov 30, 2011 at 7:56 PM, James Cook [jcook@pykl.com](mailto:jcook@pykl.com) wrote: > Yes, mapping was wrong. I didn't realize it referenced mapping files. > Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:46am UTC](https://discuss.elastic.co/t/jackson-error-parsing-json/6029/5 "2017-07-06T03:46:50Z")