apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Hyde (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (APEXMALHAR-1818) Integrate Calcite to support SQL
Date Mon, 25 Jul 2016 04:59:20 GMT

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

Julian Hyde edited comment on APEXMALHAR-1818 at 7/25/16 4:59 AM:
------------------------------------------------------------------

Sounds basically good. Remember, the syntax for a streaming query in Calcite includes the
{{STREAM}} keyword, e.g. {{SELECT STREAM * FROM Orders WHERE productId = 100}}, so that if
{{Orders}} is a dual stream/table you can write {{SELECT * FROM Orders}} to get the historical
orders.

There are unit tests in Calcite, {{StreamTest}} and {{CsvTest.testCsvStream}}, that indicate
how a streaming query is parsed, planned and executed. You would substitute your own implementation
of Table, and write a version of Filter that generates an Apex plan (though I'm not sure what
that looks like).


was (Author: julianhyde):
Sounds basically good. Remember, the syntax for a streaming query in Calcite includes the
{{STREAM}} keyword, e.g. {{SELECT STREAM * FROM Orders WHERE productId = 100}}, so that if
Orders is a dual stream/table you can write {{SELECT * FROM Orders}} to get the historical
orders.

There are unit tests in Calcite, StreamTest and CsvTest.testCsvStream, that indicate how a
streaming query is parsed, planned and executed. You would substitute your own implementation
of Table, and write a version of Filter that generates an Apex plan (though I'm not sure what
that looks like).

> Integrate Calcite to support SQL
> --------------------------------
>
>                 Key: APEXMALHAR-1818
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-1818
>             Project: Apache Apex Malhar
>          Issue Type: New Feature
>          Components: query operators
>            Reporter: Amol
>              Labels: roadmap
>
> Once we have ability to generate a subdag, we should take a look at integrating Calcite
into Apex. The operator that enables populate DAG, should use Calcite to generate the DAG,
given a SQL query.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message