Property value on field - Common causes and quick fixes

Property value on field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.1-7.15

value] is unsupported. Briefly, this error occurs when you are trying to use a property on a field that Elasticsearch does not support. This could be due to a typo, using a deprecated property, or using a property that is not applicable to the field’s data type. To resolve this issue, you should first check the Elasticsearch documentation to ensure that the property is valid. If it is, ensure that it is spelled correctly and is applicable to the field’s data type. If the property is deprecated, you will need to find and use the updated property.

This guide will help you check for common problems that cause the log ” Property [value] on field [ ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Property [value] on field [” class name is ConstantKeywordFieldMapper.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // This is defined as updateable because it can be updated once; from [null] to any value;
 // by a dynamic mapping update.  Once it has been set; however; the value cannot be changed.
 private final Parameter value = new Parameter<>("value"; true; () -> null;
 (n; c; o) -> {
 if (o instanceof Number == false && o instanceof CharSequence == false) {
 throw new MapperParsingException("Property [value] on field [" + n +
 "] must be a number or a string; but got [" + o + "]");
 }
 return o.toString();
 }; m -> toType(m).fieldType().value);
 private final Parameter> meta = Parameter.metaParam();