You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2020/02/24 15:20:00 UTC

[jira] [Closed] (FLINK-16067) Flink's CalciteParser swallows error position information

     [ https://issues.apache.org/jira/browse/FLINK-16067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Wysakowicz closed FLINK-16067.
------------------------------------
    Resolution: Fixed

Fixed in:
master: f3415d74212e765cbd189c73147289c1f6ba451f
1.10.1: 6f82b251669dff6c84f1045c803050ca47f8db17

> Flink's CalciteParser swallows error position information
> ---------------------------------------------------------
>
>                 Key: FLINK-16067
>                 URL: https://issues.apache.org/jira/browse/FLINK-16067
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>    Affects Versions: 1.10.0
>            Reporter: Fabian Hueske
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.1, 1.11.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The parser used to parse SQL queries submitted through {{TableEnvironmentImpl.sqlUpdate}} does not add the original exception from Calcite as a cause to Flink's {{org.apache.flink.table.api.SqlParserException}}. 
> However, Calcite's exception contains the position in the SQL query where the parser failed.
> This info would help users to fix their queries.
> This used to work with Flink 1.9.x.
> CC [~dwysakowicz]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)