You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "chenliang613 (JIRA)" <ji...@apache.org> on 2016/01/14 20:23:39 UTC

[jira] [Commented] (FLINK-2099) Add a SQL API

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

chenliang613 commented on FLINK-2099:
-------------------------------------

Ya, TPC-DS should be widely used benchmark for SQL on Hadoop solutions. 
As my experience, supports the SQL syntax would be not big problem, but the performance would be the major challenges, please consider it more. 

Thanks
Liang

> Add a SQL API
> -------------
>
>                 Key: FLINK-2099
>                 URL: https://issues.apache.org/jira/browse/FLINK-2099
>             Project: Flink
>          Issue Type: New Feature
>          Components: Table API
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>              Labels: requires-design-doc
>
> From the mailing list:
> Fabian: Flink's Table API is pretty close to what SQL provides. IMO, the best
> approach would be to leverage that and build a SQL parser (maybe together
> with a logical optimizer) on top of the Table API. Parser (and optimizer)
> could be built using Apache Calcite which is providing exactly this.
> Since the Table API is still a fairly new component and not very feature
> rich, it might make sense to extend and strengthen it before putting
> something major on top.
> Ted: It would also be relatively simple (I think) to retarget drill to Flink if
> Flink doesn't provide enough typing meta-data to do traditional SQL.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)