flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5280) Extend TableSource to support nested data
Date Tue, 10 Jan 2017 10:08:58 GMT

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

ASF GitHub Bot commented on FLINK-5280:

Github user mushketyk commented on a diff in the pull request:

    --- Diff: flink-libraries/flink-table/src/main/scala/org/apache/flink/table/sources/TableSource.scala
    @@ -19,22 +19,23 @@
     package org.apache.flink.table.sources
     import org.apache.flink.api.common.typeinfo.TypeInformation
    +import org.apache.flink.table.api.TableEnvironment
    -/** Defines an external table by providing schema information, i.e., field names and
    +/** Defines an external table by providing schema information and used to produce a
    +  * [[org.apache.flink.api.scala.DataSet]] or [[org.apache.flink.streaming.api.scala.DataStream]].
    +  * Schema information consists of a data type, field names, and corresponding indices
    +  * these names in the data type.
    +  *
    +  * To define a TableSource one need to implement [[TableSource#getReturnType]]. In this
    +  * field names and field indices are derived from the returned type.
    +  *
    +  * In case if custom field names are required one need to additionally implement
    --- End diff --
    I am not sure about this. I've checked it with [Grammarly](grammarly.com) and it does
not complain about "In case if", but complains about the "in case of".

> 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

View raw message