[
https://issues.apache.org/jira/browse/FLINK-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581644#comment-14581644
]
Fabian Hueske commented on FLINK-2099:
--------------------------------------
That looks nice. :-)
I would make the registration a separate method on the TableEnvironment to
reduce duplicated methods and allow the registration of derived tables. We
could also add a method to register a full HCatalog and to get registered
tables such as
{code}
DataSet<Invoice> invoices = ...
TableEnvironment tEnv = ...
Table invoicesT = tEnv.fromDataSet(invoices);
tEnv.registerHCatalog(hCatConf);
tEnv.registerTable(invoicesT, "invoices")
Table users = tEnv.getTable("users"); // from HCatalog
{code}
> 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)
