No value specified for terms query – How to solve this Elasticsearch error

No value specified for terms query – How to solve this Elasticsearch error

Opster Team

February-21, Version: 1.7-8.0

To understand why a value needs to be specified for a term query and how to avoid this error in the future, you should run the Elasticsearch Error Check-Up.

This guide will help you understand common problems and related issues that cause the log “No value specified for terms query” to appear. To get started, read the general overview on the Elasticsearch concepts: query and index.

Background

A terms query returns documents that contain one or more exact terms in a provided field. The above exception arises when you try to find a document where the field contains null. 

If you need to get the field that has only a null value using a query, then you can use the must_not exists filter

How to reproduce this exception

Create Index

PUT /my-index
{
 "mappings": {
   "properties": {
     "name": {
       "type": "keyword"
     }
   }
 }
}

Index Data

PUT /my-index/_doc/1?pretty
{
 "name": "john"
}}

Search Query

POST /my-index/_search
{
 "query": {
   "terms": {
     "name": [
       "john",
       "jack",
       null
     ]
   }
 }
}

Search Response

{
 "error": {
   "root_cause": [
     {
       "type": "parsing_exception",
       "reason": "No value specified for terms query",
       "line": 7,
       "col": 9
     }
   ],
   "type": "parsing_exception",
   "reason": "No value specified for terms query",
   "line": 7,
   "col": 9
 },
 "status": 400
}

How to fix this exception

Elasticsearch reported this error because querying an array with null value doesn’t work in terms query.

To correct the issue, you need to modify the search query as shown below:

POST /my-index/_search
{
 "query": {
   "terms": {
     "name": [
       "john",
       "jack"
     ]
   }
 }
}

Log Context

Log”No value specified for terms query”classname  is TermsQueryBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

static List parseValues(XContentParser parser) throws IOException {
  List values = new ArrayList();
  while (parser.nextToken() != XContentParser.Token.END_ARRAY) {
  Object value = maybeConvertToBytesRef(parser.objectBytes());
  if (value == null) {
  throw new ParsingException(parser.getTokenLocation(); "No value specified for terms query");
  }
  values.add(value);
  }
  return values;
  }

Run the Check-Up to get customized recommendations like this:

error

Heavy merges detected in specific nodes

error-img

Description

A large number of small shards can slow down searches and cause cluster instability. Some indices have shards that are too small…

error-img

Recommendations Based on your specific ES deployment you should…

Based on your specific ES deployment you should…

1

X-PUT curl -H [a customized recommendation]

 

Optimize Elasticsearch Performance

Try The Tool