[
https://issues.apache.org/jira/browse/FLINK-24908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser updated FLINK-24908:
-----------------------------------
Release Note: Parse errors now state the position and echo the failing line
with carets under it, before the parser's own text. Sensitive option values on
that line are masked, including keys listed in
security.redaction.additional-keys. The SQL client prints the outermost
exception that ends with the root cause's message instead of the root cause
itself. Tools that match on the text directly after "SQL parse failed." need to
be adapted.
> Improve SQL Error description for SQL Client
> --------------------------------------------
>
> Key: FLINK-24908
> URL: https://issues.apache.org/jira/browse/FLINK-24908
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Client
> Reporter: Sergey Nuyanzin
> Assignee: Martijn Visser
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> For instance for misprint like
> {code:sql}
> ELECT 1;
> {code}
> The error looks like
> {noformat}
> ELECT 1;
> [ERROR] Could not execute SQL statement. Reason:
> org.apache.calcite.runtime.CalciteException: Non-query expression encountered
> in illegal context
> {noformat}
> At the same time ParseException wrapped by CalciteException contains position
> of a problem word
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
