[
https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740517#comment-15740517
]
Ivan Mushketyk commented on FLINK-5280:
---------------------------------------
Thank you [~fhueske].
The general idea seems feasible, but I still have few conceptual questions:
* Isn't *FlatTableSource* just an edge case of a *NestedTableSource*?
* Why do we need two different table source types in the first place? Is it
because we need to register flat schema and nested schema in a different way?
If so would a flag/enum be a better alternative to distinguish between
flat/nested types?
I also have a more technical question. I spend some time looking throught the
*flink-table* and *Calcite* sources, but I wasn't able to find an example of
how to register a nested field in Calcite (I assume we don't do this already).
Do you know where I can find an example for this?
> 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)
