[
https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15741391#comment-15741391
]
Fabian Hueske commented on FLINK-5280:
--------------------------------------
Thanks for the questions [~ivan.mushketyk].
It is true. {{FlatTableSource}} would be a special case of
{{NestedTableSource}}. I proposed this structure mainly to limit the changes to
the API. On the other hand, I don't think that this interface has been used a
lot and it is rather an internal interface. Flat and nested tables are
registered the same, however, the definition of nested schema is a bit more
complex. If we design a good API for nested schema, we can also keep a single
interface.
I think we do register tables with nested schema when a DataSet with nested
types (such as a Tuple nested in a Tuple) is converted into a Table.
> 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)
