# MapperParsingException\[No handler for type \[ınteger\] declared on field \[favoriteIntNumber\]\]

**URL:** <https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007>\
**Category:** Elasticsearch\
**Created:** [November 6, 2015, 3:55pm UTC](https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007 "2015-11-06T15:55:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zoltan](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zoltan](https://discuss.elastic.co/u/zoltan)\
**Post date:** [November 6, 2015, 3:55pm UTC](https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007/1 "2015-11-06T15:55:47Z")

</div>

Could this be a classpath error? Any ideas?

MapperParsingException[No handler for type [ınteger] declared on field [favoriteIntNumber]] at \_\_randomizedtesting.SeedInfo.seed([AF0C2FA73F396B56: No handler for type [ınteger] declared on field [favoriteIntNumber]  
MapperParsingException[No handler for type [ınteger] declared on field [favoriteIntNumber]]  
at \_\_randomizedtesting.SeedInfo.seed([AF0C2FA73F396B56:4A57EA4524160FFC]:0)  
at org.elasticsearch.index.mapper.object.ObjectMapper$TypeParser.parseProperties(ObjectMapper.java:313)  
at org.elasticsearch.index.mapper.object.ObjectMapper$TypeParser.parseObjectOrDocumentTypeProperties(ObjectMapper.java:228)  
at org.elasticsearch.index.mapper.object.RootObjectMapper$TypeParser.parse(RootObjectMapper.java:137)  
at org.elasticsearch.index.mapper.DocumentMapperParser.parse(DocumentMapperParser.java:211)  
at org.elasticsearch.index.mapper.DocumentMapperParser.parseCompressed(DocumentMapperParser.java:192)  
at org.elasticsearch.index.mapper.MapperService.parse(MapperService.java:368)  
at org.elasticsearch.cluster.metadata.MetaDataMappingService$2.execute(MetaDataMappingService.java:382)  
at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:388)  
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:225)  
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:188)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)

---

<div class="post-metadata">

**Author:** ![rmuir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rmuir/32/44949_2.png) [@rmuir](https://discuss.elastic.co/u/rmuir)\
**Post date:** [November 6, 2015, 11:54pm UTC](https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007/2 "2015-11-06T23:54:18Z")

</div>

looks like a turkish locale issue somewhere.

---

<div class="post-metadata">

**Author:** ![zoltan](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zoltan](https://discuss.elastic.co/u/zoltan)\
**Post date:** [November 9, 2015, 7:36am UTC](https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007/3 "2015-11-09T07:36:35Z")

</div>

It has nothing to do with Turkish locale because of two reasons. It runs under US locale and it complains that it can't map an int field during insertion with Java API 🙂

Anyway it looks like that -ea jvm option solves this issue.

---

<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:** [July 5, 2017, 11:39pm UTC](https://discuss.elastic.co/t/mapperparsingexception-no-handler-for-type-integer-declared-on-field-favoriteintnumber/34007/4 "2017-07-05T23:39:51Z")

</div>