Kibana 5 getting console exception "cannot be changed from type [long] to [integer]" when clicking on Timelion Tab

[binodsuman]

Kibana Version: 5.0.0
ElasticSearch Version: 5.0.0
Server OS version:
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 4
Browser version: Chrome Version 55.0.2883.87 m but Reproducible on all kind of Browser.

Original install method (e.g. download page, yum, from source, etc.): from source

Steps to reproduce:

1. Install fresh or upgrade Kibana 5.0.0
2. Install fresh or upgrade Elasticsearch 5.0.0
3. Pumping data into ES using template
4. Make sure all data come on Kibana Dashboard
5. Now click on Timelion Tab

Blank page comes when clicking on Timelion. But getting exception in Elasticsearch console:

java.lang.IllegalArgumentException: mapper [hits] cannot be changed from type [long] to [integer]
at org.elasticsearch.index.mapper.MappedFieldType.checkTypeName(MappedFieldType.java:144) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.MappedFieldType.checkCompatibility(MappedFieldType.java:156) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.LegacyNumberFieldMapper$NumberFieldType.checkCompatibility(LegacyNumberFieldMapper.java:133) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.FieldTypeLookup.checkCompatibility(FieldTypeLookup.java:128) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.FieldTypeLookup.copyAndAddAll(FieldTypeLookup.java:94) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:324) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.index.mapper.MapperService.merge(MapperService.java:277) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.applyRequest(MetaDataMappingService.java:323) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cluster.metadata.MetaDataMappingService$PutMappingExecutor.execute(MetaDataMappingService.java:241) ~[elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cluster.service.ClusterService.runTasksForExecutor(ClusterService.java:555) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.cluster.service.ClusterService$UpdateTask.run(ClusterService.java:894) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:444) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:237) [elasticsearch-5.0.0.jar:5.0.0]
at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:200) [elasticsearch-5.0.0.jar:5.0.0]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_112]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_112]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_112]

[Bargs]

Probably the same issue #9888

[jbudz]

Confirming same issue, closing in favor of #9888. It's usually caused by the kibana index being pushed before mappings are defined.