-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trying to merge the field stats of field but the field type is incompatible #18135
Comments
Trying to work up a recreation |
OK - simple recreation. Start a cluster with two nodes, then run the following:
The above returns:
With the following stack trace:
|
This is a serialization bug in the field stats transport that was introduced when the new point api was added. It occurs only with 5.0.0-alpha2 and has been fixed in master with this commit f600c4a |
@jimferenczi this effectively prevents, at least in my environment, any use in kibana of the data coming from logstash. just raising a concern that this might impede proper testing of alpha2 through our user base |
@nellicus yeah - not much we can do about it until the next release |
This also occurred when I tried to use the winlogbeat indexes on a fresh installation without Logstash |
Will adding "format" : "date_time" to the mapping for the index created by logstash stop this error? |
@gluckspilz: for me doesn't work 👎 |
This is fixed in 5.0.0-alpha3, which is out already |
linked to elastic/kibana#7127
Elasticsearch version:
5.0.0-alpha2
JVM version:
java version "1.8.0_45"
OS version:
Linux
Description of the problem including expected versus actual behavior:
Error when calling _field_stats API on Logstash 5.0.0-alpha2 generated index
calling the same on .monitoring-es-* index timestamp field works ok
Provide logs (if relevant):
**other info
@timestamp mapping for problematic logstash-syslog-* index
timestamp mapping for .monitoring-es-* index
The text was updated successfully, but these errors were encountered: