flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ovidiu Marcu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2099) Add a SQL API
Date Tue, 08 Dec 2015 10:36:11 GMT

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

Ovidiu Marcu commented on FLINK-2099:
-------------------------------------

Hi Timo,
Thank you for your detailed response.
For the benchmark you want to use, I am not sure if TPC-H is the best to follow, as the new
benchmark TPC-DS (next generation decision support) is developed to handle the deficiencies
of TPC-H (reference here http://www.tpc.org/tpcds/presentations/The_Making_of_TPCDS.pdf)
I would like to help/contribute, I will look into your branch and come back to you.

I think this is one the most important features of Flink, I don't know why Flink guys don't
want to increase its priority and give more attention.

Best regards,
Ovidiu

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

Mime
View raw message