Briefly, this error occurs when Elasticsearch attempts to read a custom metadata field expecting a long integer, but the actual value is not a valid long. This could be due to incorrect data type or format. To resolve this issue, you can: 1) Check the data input and ensure it’s a valid long integer. 2) Modify the mapping of the index to correctly define the data type of the field. 3) Use a script or ingest pipeline to transform the data into the correct format before indexing.
This guide will help you check for common problems that cause the log ” Custom metadata field [{}] does not contain a valid long. Actual value: [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, metadata, long.
Overview
Metadata in Elasticsearch refers to additional information stored for each document. This is achieved using the specific metadata fields available in Elasticsearch. The default behavior of some of these metadata fields can be customized during mapping creation.
Examples
Using _meta meta-field for storing application-specific information with the mapping:
PUT /my_index?pretty
{
"mappings": {
"_meta": {
"domain": "security",
"release_information": {
"date": "18-01-2020",
"version": "7.5"
}
}
}
}Notes
- In version 2.x, Elasticsearch had a total 13 meta fields available, which are: _index, _uid, _type, _id, _source, _size, _all, _field_names, _timestamp, _ttl, _parent, _routing, _meta
- In version 5.x, _timestamp and _ttl meta fields were removed.
- In version 6.x, the _parent meta field was removed.
- In version 7.x, _uid and _all meta fields were removed.
Log Context
Log “Custom metadata field [{}] does not contain a valid long. Actual value: [{}]” class name is LifecycleExecutionState.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
}
if (customData.containsKey(INDEX_CREATION_DATE)) {
try {
builder.setIndexCreationDate(Long.parseLong(customData.get(INDEX_CREATION_DATE)));
} catch (NumberFormatException e) {
throw new ElasticsearchException("Custom metadata field [{}] does not contain a valid long. Actual value: [{}]";
e; INDEX_CREATION_DATE; customData.get(INDEX_CREATION_DATE));
}
}
if (customData.containsKey(PHASE_TIME)) {
try {
[ratemypost]