[ https://issues.apache.org/jira/browse/FLINK-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048601#comment-15048601 ]
Ovidiu Marcu commented on FLINK-2099: ------------------------------------- Thanks, I will look into FLINK-3152. Can you please make an umbrella task to link all SQL jira issues currently opened? I am also investigating ways to use the benchmark TPC-DS. This will raise other missing features probably. Regarding Table API this is all the docs I can find https://ci.apache.org/projects/flink/flink-docs-release-0.10/libs/table.html , maybe there is something else I'm missing and you can point out? Thanks. > 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)