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

Konstantin Knauf updated FLINK-9814:
------------------------------------
    Issue Type: Improvement  (was: Wish)

As part of https://issues.apache.org/jira/browse/FLINK-22029 the "Wish" issue 
type will be dropped. I changed this one to "Improvement" instead.

> CsvTableSource "lack of column" warning
> ---------------------------------------
>
>                 Key: FLINK-9814
>                 URL: https://issues.apache.org/jira/browse/FLINK-9814
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Ecosystem
>    Affects Versions: 1.5.0
>            Reporter: François Lacombe
>            Priority: Minor
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> The CsvTableSource class is built by defining expected columns to be find in 
> the corresponding csv file.
>  
> It would be great to throw an Exception when the csv file doesn't have the 
> same structure as defined in the source. For retro-compatibility sake, 
> developers should explicitly set the builder to define columns stricly and 
> expect Exception to be thrown in case of structure difference.
> It can be easilly checked with file header if it exists.
> Is this possible ?



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

Reply via email to