java.lang.IllegalArgumentException

Mapper for [hits] conflicts with existing mapping in other types: [mapper [hits] cannot be changed from type [long] to [int]]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web25090

  • via GitHub by abcfy2
    , 1 year ago
    Mapper for [hits] conflicts with existing mapping in other types: [mapper [hits] cannot be changed from type [long] to [int]]
  • via GitHub by abcfy2
    , 1 year ago
    Mapper for [hits] conflicts with existing mapping in other types: [mapper [hits] cannot be changed from type [long] to [int]]
  • Mapper for [version] conflicts with existing mapping in other types: [mapper [version] cannot be changed from type [long] to [int]]
  • Stack trace

    • java.lang.IllegalArgumentException: Mapper for [hits] conflicts with existing mapping in other types: [mapper [hits] cannot be changed from type [long] to [int]] at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(FieldTypeLookup.java:117) at org.elasticsearch.index.mapper.MapperService.checkNewMappersCompatibility(MapperService.java:364) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:315) at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:261) at org.elasticsearch.cluster.metadata.MetaDataMappingService$2.execute(MetaDataMappingService.java:444) at org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:388) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:231) at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:194) 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)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago