flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Walther (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-2099) Add a SQL API
Date Wed, 27 May 2015 12:32:18 GMT
Timo Walther created FLINK-2099:

             Summary: 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

View raw message