flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jark Wu (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FLINK-5280) Extend TableSource to support nested data
Date Thu, 22 Dec 2016 13:08:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15770018#comment-15770018
] 

Jark Wu edited comment on FLINK-5280 at 12/22/16 1:08 PM:
----------------------------------------------------------

Hi guys,

It is a very good extension of the discussion. It seems that I'm late for the discussion :).
I will still post my ideas below.

I think {{getFieldTypes()}} and {{getNumberOfFields()}} can be derived from {{getReturnType()}}
all the time. So I would like to move them into util class, it will make the interface clean.
Actually, we already have one called {{UserDefinedFunctionUtil.getFieldInfo(TypeInformation)}}
and {{TableEnvironment.getFieldInfo(TypeInformation)}} which returns field types and names
and indicies. We can refactor them and move them to a better place and maybe add split variant
(i.e. {{getFieldNames}}, {{getFieldIndicies}}, {{getFieldTypes}}).

And provide the default implementation of {{getFieldNames}} and {{getFieldIndicies}} based
on the util.



was (Author: jark):
Hi guys,

It is a very good extension of the discussion. It seems that I'm late for the discussion :).
I will still post my ideas below.

I think {{getFieldTypes()}} and {{getNumberOfFields()}} can be derived from {{getReturnType()}}
all the time. So I would like to move them into util class, it will make the interface clean.
Actually, we already have one called {{UserDefinedFunctionUtil.getFieldInfo(TypeInformation)}}
and {{TableEnvironment.getFieldInfo(TypeInformation)}} which returns field types and names
and indicies. We can refactor them and move them to a better place and maybe split variant
(i.e. {{getFieldNames}}, {{getFieldIndicies}}, {{getFieldTypes}}).

And provide the default implementation of {{getFieldNames}} and {{getFieldIndicies}} based
on the util.


> 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)

Mime
View raw message