All String join - Common causes and quick fixes

All String join – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

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.

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 RestGetMappingAction.java. 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) {
 builder.close();
 throw new TypeMissingException("_all"; String.join(";"; types));
 }  builder.startObject();
 {
 if (missingTypes.isEmpty() == false) {