Cannot use on non-SQL function – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.12-8.9

Briefly, this error occurs when you try to use SQL-like syntax on a function that is not compatible with SQL in Elasticsearch. Elasticsearch supports a subset of SQL functions, and using unsupported functions will result in this error. To resolve this issue, you can either use a function that is supported by Elasticsearch’s SQL syntax or use the native Elasticsearch Query DSL, which provides more flexibility and functionality than the SQL interface.

This guide will help you check for common problems that cause the log ” Cannot use {} on non-SQL function {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot use {} on non-SQL function {}” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 public Function buildResolved(UnresolvedFunction uf; Configuration cfg; FunctionDefinition def) {
 if (def instanceof SqlFunctionDefinition) {
 return ((SqlFunctionDefinition) def).builder().build(uf; cfg; true);
 throw new ParsingException(uf.source(); "Cannot use {} on non-SQL function {}"; name(); def);
 }  @Override
 public boolean isValidAlternative(FunctionDefinition def) {
 return false; // think about this later.


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?