# Parsing exception after upgrade to version 6

**URL:** <https://discuss.elastic.co/t/parsing-exception-after-upgrade-to-version-6/108157>\
**Category:** Elasticsearch\
**Created:** [November 17, 2017, 4:03pm UTC](https://discuss.elastic.co/t/parsing-exception-after-upgrade-to-version-6/108157 "2017-11-17T16:03:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nadir](https://avatars.discourse-cdn.com/v4/letter/n/e5b9ba/32.png) [@Nadir](https://discuss.elastic.co/u/Nadir)\
**Post date:** [November 17, 2017, 4:03pm UTC](https://discuss.elastic.co/t/parsing-exception-after-upgrade-to-version-6/108157/1 "2017-11-17T16:03:55Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 18, 2017, 9:31am UTC](https://discuss.elastic.co/t/parsing-exception-after-upgrade-to-version-6/108157/2 "2017-11-18T09:31:26Z")

</div>

It looks like your request is not structured correctly and therefore not a valid JSOn request. Look at it using [jsonlint](https://jsonlint.com) and you will see what I mean.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 16, 2017, 9:31am UTC](https://discuss.elastic.co/t/parsing-exception-after-upgrade-to-version-6/108157/3 "2017-12-16T09:31:27Z")

</div>

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