Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.
Briefly, this error occurs when Elasticsearch encounters an incorrect value for the day of the week in a date histogram aggregation. The value should be a string (like “Monday”) or a number (1-7), but a different type of value or an out-of-range number was found. To resolve this, ensure that the day of the week value is correctly formatted. If it’s a string, it should be the full name of the day, and if it’s a number, it should be within the range of 1-7, where 1 is Monday and 7 is Sunday.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” invalid weekly day value. expected a string or a number value; but found [” + token + “] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “invalid weekly day value. expected a string or a number value; but found [” + token + “]” class name is WeekTimes.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
return DayOfWeek.resolve(parser.text());
}
if (token == XContentParser.Token.VALUE_NUMBER) {
return DayOfWeek.resolve(parser.intValue());
}
throw new ElasticsearchParseException("invalid weekly day value. expected a string or a number value; but found [" + token + "]");
} public static class Builder { private final Set days = new HashSet<>();
