[
https://issues.apache.org/jira/browse/FLINK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552715#comment-16552715
]
François Lacombe commented on FLINK-9814:
-----------------------------------------
I agree for the check on a single files, since exceptions are thrown for a
given file and not every found file.
I need to practice a little more Flink to think properly about the process :)
{quote}
only the field names may be encoded in the header.
{/quote}
Yes type information doesn't come in CSV header.
I was talking of different file formats like dbf (shape file) or Avro records
where you can check the type.
Basically, check operations depends on format capabilities. Precisely for CSV,
only fields names could be checked.
> CsvTableSource "lack of column" warning
> ---------------------------------------
>
> Key: FLINK-9814
> URL: https://issues.apache.org/jira/browse/FLINK-9814
> Project: Flink
> Issue Type: Wish
> Components: Table API & SQL
> Affects Versions: 1.5.0
> Reporter: François Lacombe
> Assignee: vinoyang
> 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
(v7.6.3#76005)
