You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2017/09/05 14:08:00 UTC

[jira] [Closed] (FLINK-7572) Improve TableSchema ValidationException message.

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

Fabian Hueske closed FLINK-7572.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.3
                   1.4.0

Fixed for 1.3.3 with 0e2e9cb55255cd942fa33aff888038c8d8858307
Fixed for 1.4.0 with 0eef8e8c01041bb0c001282a16c43ea54f859cfa

> Improve TableSchema ValidationException message.
> ------------------------------------------------
>
>                 Key: FLINK-7572
>                 URL: https://issues.apache.org/jira/browse/FLINK-7572
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: sunjincheng
>            Assignee: sunjincheng
>             Fix For: 1.4.0, 1.3.3
>
>
> When sql is very complicated(e.g.: more than 100+ tables), the following exception information is very confusing:
> {code}
> org.apache.flink.table.api.TableException: Table column names must be unique. at org.apache.flink.table.api.TableSchema.<init>(TableSchema.scala:36)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)