Pipe expects exactly one argument but found – 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 Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Pipe expects exactly one argument but found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: parser and plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

Log Context

Log “Pipe [{}] expects exactly one argument but found [{}]”classname  is LogicalPlanBuilder.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 private Expression pipeIntArgument(Source source; String pipeName; List exps) {
 int size = CollectionUtils.isEmpty(exps) ? 0 : exps.size();
 if (size != 1) {
 throw new ParsingException(source; "Pipe [{}] expects exactly one argument but found [{}]"; pipeName; size);
 BooleanExpressionContext limitCtx = exps.get(0);
 Expression expression = expression(limitCtx); 
 if (expression.dataType().isInteger() == false || expression.foldable() == false || (int) expression.fold() < 0) {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content