[
https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15804341#comment-15804341
]
ASF GitHub Bot commented on FLINK-5280:
---------------------------------------
Github user wuchong commented on the issue:
https://github.com/apache/flink/pull/3039
I like this idea. In this way, we only need to provide `BatchTableSource`
and `StreamTableSource` interfaces, not involving the odd
`BatchStreamTableSource`. We can keep the interface very clean.
If I understand right, all the concrete implementation of `TableSource`
will not implement `DefinesFieldNames` for now ?
> Extend TableSource to support nested data
> -----------------------------------------
>
> Key: FLINK-5280
> URL: https://issues.apache.org/jira/browse/FLINK-5280
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.2.0
> Reporter: Fabian Hueske
> Assignee: Ivan Mushketyk
>
> The {{TableSource}} interface does currently only support the definition of
> flat rows.
> However, there are several storage formats for nested data that should be
> supported such as Avro, Json, Parquet, and Orc. The Table API and SQL can
> also natively handle nested rows.
> The {{TableSource}} interface and the code to register table sources in
> Calcite's schema need to be extended to support nested data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
