Malformed – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch receives a request with incorrect or malformed syntax. This could be due to incorrect JSON formatting, incorrect field names, or incorrect query syntax. To resolve this issue, you should first check the syntax of your request to ensure it’s correct. If the syntax is correct, check the field names and data types in your request. If these are correct, check your query syntax. If you’re still experiencing issues, consider using a tool to validate your JSON or consult the Elasticsearch documentation for more information on correct request formatting.

This guide will help you check for common problems that cause the log ” malformed [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: aggregations, search.

Log Context

Log “malformed [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (Double.isNaN(lon)) {
 lon = parser.doubleValue();
 } else if (Double.isNaN(lat)) {
 lat = parser.doubleValue();
 } else {
 throw new ParsingException(parser.getTokenLocation(); "malformed [" + ORIGIN_FIELD.getPreferredName()
 + "]: a geo point array must be of the form [lon; lat]");
 return new GeoPoint(lat; lon);