[
https://issues.apache.org/jira/browse/FLINK-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046761#comment-15046761
]
Fabian Hueske commented on FLINK-2099:
--------------------------------------
Hi Ovidiu,
thanks for your interest in Flink and welcome to the community! It would be
awesome if you'd start to contribute.
Support for TPC-D would definitely be very nice, but I think TPC-H is a good
starting point because it is less complex (22 vs. 99 queries) and covers
already quite a lot of the SQL space.
Regarding the priority of features, my opinion is that there is an abundance of
SQL-on-Hadoop solutions but a need for stream processors with a good feature
set. I (and other members of the community) believe that this is the area where
Flink can provide the best benefit to users.
Of course support for SQL is an awesome feature to have for Flink and I am very
happy that people are working on it.
Best, Fabian
> 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)
