All String join – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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 Elasticsearch operation.

Briefly, this error occurs when the “_all” field is used in Elasticsearch versions 6.0 and above, where it has been deprecated. The “_all” field was used to search across all fields in a document. To resolve this issue, you can use the “copy_to” feature to copy the fields you want to a single combined field and search on that. Alternatively, you can use a custom “all” field that’s a concatenation of the fields you want to search. Lastly, you can use the “_source” field to search across all fields.

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 ” _all”; String.join(“; ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: indices, rest, admin.

Log Context

Log “_all”; String.join(“;” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 }  final ImmutableOpenMap> mappingsByIndex = response.getMappings();
 if (mappingsByIndex.isEmpty() && types.length != 0) {
 throw new TypeMissingException("_all"; String.join(";"; types));
 }  builder.startObject();
 if (missingTypes.isEmpty() == false) {


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?