Pattern must not be null – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Pattern must not be null ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Log Context

Log “Pattern must not be [null]”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

return null;
 String pattern = string(ctx.value);
 if (pattern == null) {
 throw new ParsingException(source(ctx.value); "Pattern must not be [null]");
 int pos = pattern.indexOf('*');
 if (pos >= 0) {
 throw new ParsingException(source(ctx.value);
 "Invalid char [*] found in pattern [{}] at position {}; use [%] or [_] instead";


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content