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


(Zoltan Toth) #1

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)


#2

looks like a turkish locale issue somewhere.


(Zoltan Toth) #3

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 :slight_smile:

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


(system) #4