Parsing exception after upgrade to version 6

Elastic Stack Elasticsearch
1

After upgrading my cluster to version 6 I got a lot of problems with the queries.

What is wrong with this query ?

{"search_type":"query_then_fetch","ignore_unavailable":true,"index":["metricbeat-2017.11.17"]} {"size":0,"query":{"bool":{"filter":[{"range":{"@timestamp":{"gte":"1510911836404","lte":"1510933436404","format":"epoch_millis"}}},{"query_string":{"analyze_wildcard":true,"query":"beat.hostname:"/ge-ham-sdc06/" AND metricset.name:"memory""}}]}},"aggs":{"2":{"date_histogram":{"interval":"5m","field":"@timestamp","min_doc_count":0,"extended_bounds":{"min":"1510911836404","max":"1510933436404"},"format":"epoch_millis"},"aggs":{"1":{"max":{"field":"system.memory.used.pct","missing":0}}}}}}

This is the response I get:

{
"error": {
"root_cause": [
{
"type": "parsing_exception",
"reason": "Unknown key for a VALUE_STRING in [search_type].",
"line": 1,
"col": 16
}
],
"type": "parsing_exception",
"reason": "Unknown key for a VALUE_STRING in [search_type].",
"line": 1,
"col": 16
},
"status": 400
}

This is showing up if I use the Dev Tools in Kibana 6.

Any idea ?

Kind regards,
Thorsten

2

It looks like your request is not structured correctly and therefore not a valid JSOn request. Look at it using jsonlint and you will see what I mean.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.