Can t round a GEO POINT – How to solve this OpenSearch exception

Opster Team

Aug-23, Version: 1-2.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.

Briefly, this error occurs when there’s an attempt to round a GEO POINT field in OpenSearch. GEO POINT fields store geographical locations and cannot be rounded like numerical fields. To resolve this, you should avoid applying rounding functions to GEO POINT fields. Instead, use appropriate geographical functions designed for handling such data. If you need to manipulate GEO POINT data, consider extracting the latitude and longitude values as separate numerical fields, which can then be rounded if necessary.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” can’t round a [GEO_POINT] ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: aggregations, search.

 
 

aggregations

 
 

search

Quick links

Overview

Search refers to the searching of documents in an index or multiple indices. The simple search is just a GET API request to the _search endpoint. The search query can either be provided in query string or through a request body.

Examples

When looking for any documents in this index, if search parameters are not provided, every document is a hit and by default 10 hits will be returned.

GET my_documents/_search

A JSON object is returned in response to a search query. A 200 response code means the request was completed successfully.

{
"took" : 1,
"timed_out" : false,
"_shards" : {
"total" : 2,
"successful" : 2,
"failed" : 0
},
"hits" : {
"total" : 2,
"max_score" : 1.0,
"hits" : [
...
]
}
}

Notes and good things to know

  • Distributed search is challenging and every shard of the index needs to be searched for hits, and then those hits are combined into a single sorted list as a final result.
  • There are two phases of search: the query phase and the fetch phase.
  • In the query phase, the query is executed on each shard locally and top hits are returned to the coordinating node. The coordinating node merges the results and creates a global sorted list. 
  • In the fetch phase, the coordinating node brings the actual documents for those hit IDs and returns them to the requesting client.
  • A coordinating node needs enough memory and CPU in order to handle the fetch phase.
 
 

Log Context

Log “can’t round a [GEO_POINT]” class name is ValuesSource.java. We extracted the following from OpenSearch source code for those seeking an in-depth context :

 return org.opensearch.index.fielddata.FieldData.docsWithValue(geoPoints);
 }  @Override
 public final Function roundingPreparer(IndexReader reader) throws IOException {
 throw new AggregationExecutionException("can't round a [GEO_POINT]");
 }  public abstract MultiGeoPointValues geoPointValues(LeafReaderContext context);  /**

 

How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Get expert answers on Elasticsearch/OpenSearch

Try OpsGPT Now

Related Articles

Back to all articles