[
https://issues.apache.org/jira/browse/APEXMALHAR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278580#comment-15278580
]
Julian Hyde commented on APEXMALHAR-1818:
-----------------------------------------
Sounds good. You can use Calcite as something like a pre-processor, that takes
a SQL statement and generates a DAG (as a program). So Calcite is basically
only used offline. Many people find that a nice simple model. It definitely
makes it easy to test -- you can make sure that Calcite is generating the right
DAGs and you don't need to bother running them on Apex in order to know that
Calcite (and its Apex adapter) is doing the right thing.
@thw is here at ApacheCon Big Data and he & I and [~ilganeli] are going to
discuss shortly.
> Create a Calcite operator to enable SQL commands to be run
> ----------------------------------------------------------
>
> 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
> Assignee: Amol
> Labels: roadmap
>
> Once we have ability to code generate, 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)
