PropName on runtime field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.14-7.15

Briefly, this error occurs when you’re trying to access a property that doesn’t exist on a runtime field in Elasticsearch. This could be due to a typo in the property name or the field not being properly defined. To resolve this issue, you can check the field definition in your index mapping to ensure the field exists and the property name is spelled correctly. Alternatively, you can use the exists query to check if the field exists before trying to access its properties.

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

Log Context

Log “[” + propName + “] on runtime field [” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw new MapperParsingException(
 "unknown parameter [" + propName + "] on runtime field [" + name + "] of type [" + type + "]"
 if (propNode == null && parameter.canAcceptNull() == false) {
 throw new MapperParsingException("[" + propName + "] on runtime field [" + name
 + "] of type [" + type + "] must not have a [null] value");
 parameter.parse(name; parserContext; propNode);