You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create a single dashboard with single visualization
export all objects to a file
delete .kibana index
restart kibana
create indexPattern
Go to Settings->Import and import your exported file
here everything is fine no error
try to switch to Dashboards
HERE is the error
MergeMappingException[Merge failed with failures {[mapper [version] of different type, current_type [long], merged_type [integer]]}]
I think that the issue is that by default elasticsearch is creating the mapping long for fields like
"version", "hits"
But then in _saved_dashboard.js or other services the mapping contains "integer" type for this properties
so at some point kibana is sending a PUT request to set the mapping
and elasticsearch throws an error as it can't change it from long to integer
The error is gone when I change in the source code (mapping in service classes) all properties which where integer to long
The text was updated successfully, but these errors were encountered:
rashidkpc
added
the
bug
Fixes for quality problems that affect the customer experience
label
May 21, 2015
master branch
to reproduce:
0) create the indexPattern
here everything is fine no error
HERE is the error
MergeMappingException[Merge failed with failures {[mapper [version] of different type, current_type [long], merged_type [integer]]}]
I think that the issue is that by default elasticsearch is creating the mapping long for fields like
"version", "hits"
But then in _saved_dashboard.js or other services the mapping contains "integer" type for this properties
so at some point kibana is sending a PUT request to set the mapping
and elasticsearch throws an error as it can't change it from long to integer
The error is gone when I change in the source code (mapping in service classes) all properties which where integer to long
The text was updated successfully, but these errors were encountered: