[
https://issues.apache.org/jira/browse/APEXMALHAR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390972#comment-15390972
]
Chinmay Kolhatkar commented on APEXMALHAR-1818:
-----------------------------------------------
Hi,
I had a quick discussion with thomas on this. I would like to work on this.
As a first phase I'm planning to create an Apex Module (which can generate a
sub-DAG at launch time), to convert SQL to a subDAG.
At the first, I would like to take a simple SQL statement (SELECT * FROM TABLE
WHERE CONDITION) to convert into sub DAG.
This will be a standalone operator will get added to apex DAG by developer and
based on SQL provide, convert that into a subDAG.
For eg. A -> CalciteModule -> C
will translate to
A -> Projection -> Filter -> C
One this is achieved, we can look at further phases of integration.
I've been looking into this code
(https://github.com/milinda/samza-sql/blob/master/samza-sql-planner/src/main/java/org/apache/samza/sql/QueryExecutor.java)
for example on creating a POC. Please suggest if there is a better example
that I can look at.
Also, please suggest on above approach for phase one.
Thanks,
Chinmay.
> 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)
