field type does not accept > 2 dimensions – Elasticsearch Error How To Solve Related Issues

field type does not accept > 2 dimensions – Elasticsearch Error How To Solve Related Issues

Opster Team

July-20, Version: 1.7-8.0

 

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” field type does not accept > 2 dimensions ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log Context

Log”[{}}] field type does not accept > 2 dimensions”classname  is CartesianPoint.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

if (element == 1) {
  x = subParser.floatValue();
  } else if (element == 2) {
  y = subParser.floatValue();
  } else {
  throw new ElasticsearchParseException("[{}}] field type does not accept > 2 dimensions";
  PointFieldMapper.CONTENT_TYPE);
  }
  } else {
  throw new ElasticsearchParseException("numeric value expected");
  }

 

Optimize Elasticsearch Performance

Try The Tool