Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
Description
When queries fail to parse due to errors in query syntax, an error is thrown with a list of expected operators, which include some which we do not support at present.
I understand that the SQL validation errors come from the Calcite layer. But since we do not support all operators for now (for example: INTERSECT), the message must be updated if possible, to correctly reflect what is supported.
This would make sure contradicting messages aren't thrown (for example: first complaining with parse error indicating INTERSECT is a valid operator and then upon correction, failing saying INTERSECT isn't supported).
Query failed: ParseException: Encountered ";" at line 1, column 89. Was expecting one of: <EOF> "ORDER" ... "LIMIT" ... "OFFSET" ... "FETCH" ... "UNION" ... "INTERSECT" ... "EXCEPT" ... "NOT" ... "IN" ... "BETWEEN" ... "LIKE" ... "SIMILAR" ... "=" ... ">" ... "<" ... "<=" ... ">=" ... "<>" ... "+" ... "-" ... "*" ... "/" ... "||" ... "AND" ... "OR" ... "IS" ... "MEMBER" ... "SUBMULTISET" ... "MULTISET" ... "[" ... "OVERLAPS" ... "YEAR" ... "MONTH" ... "DAY" ... "HOUR" ... "MINUTE" ... "SECOND" ... Error: exception while executing query: Failure while executing query. (state=,code=0)