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

Updated: July-20

Elasticsearch 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 causing 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 discover the cause of many errors and provides suitable actionable recommendations (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");
  }

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 elasticsearch filtering by the size of a field that is an array -views 55,827 ,score 51

Elasticsearch index much larger than the actual size of the logs it indexed? -views   6,147,score 6



Find Configuration Errors

Analyze Now