Unsupported encoding parsing annotated text – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch tries to parse annotated text with an encoding that it doesn’t support. This could be due to incorrect content type headers or incompatible character sets. To resolve this issue, ensure that the content type header matches the actual content type of the data being sent. Also, check that the character set used in your data is supported by Elasticsearch. If necessary, convert your data to a supported encoding format before sending it to Elasticsearch.

This guide will help you check for common problems that cause the log ” Unsupported encoding parsing annotated text ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: index, plugins.

Log Context

Log “Unsupported encoding parsing annotated text” class name is AnnotatedTextFieldMapper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (value != null && value.length() > 0) {
 annotations.add(new AnnotationToken(startOffset; endOffset; value));
 } catch (UnsupportedEncodingException e) {
 throw new ElasticsearchParseException("Unsupported encoding parsing annotated text"; e);
 if (lastPos < textPlusMarkup.length()) {


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?