[
https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769949#comment-15769949
]
Fabian Hueske commented on FLINK-5280:
--------------------------------------
How about the following:
* We make the {{TableEnvironment.getFieldInfo()}} methods statically
accessible, i.e., we move them in the TableEnvironment companion object and
call this method for the default implementation of
{{TableSource.getFieldNames()}} and {{TableSource.getFieldIndicies()}}. This
way we avoid code duplication.
* We remove {{getFieldTypes()}} and {{getNumberOfFields()}}. These methods are
in fact not necessary for the interface. Have a look at how a regular DataSet
is converted into a Table. The field types are extracted in {{FlinkTable}}.
{{TableSourceTable}} overrides this logic. We could simply keep the
{{FlinkTable}} logic.
> 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)
