You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2015/04/09 23:32:12 UTC
[jira] [Commented] (SAMZA-561) Translate query plan generated by
Calcite to Samza OperatorRouter
[ https://issues.apache.org/jira/browse/SAMZA-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14488318#comment-14488318 ]
Yi Pan (Data Infrastructure) commented on SAMZA-561:
----------------------------------------------------
Hi, [~milinda], I tried to apply the patch but noticed that it might be based on the samza-sql branch that is before the re-sync [~criccomini] did in SAMZA-639? Could you update the patch? I will try to get the patch applied on the previous version in samza-sql to start reviewing it as well.
Thanks!
> Translate query plan generated by Calcite to Samza OperatorRouter
> -----------------------------------------------------------------
>
> Key: SAMZA-561
> URL: https://issues.apache.org/jira/browse/SAMZA-561
> Project: Samza
> Issue Type: Sub-task
> Components: sql
> Affects Versions: 0.9.0
> Reporter: Milinda Lakmal Pathirage
> Assignee: Milinda Lakmal Pathirage
> Labels: design, project
> Attachments: Query_Planner_SAMZA_561-0.pdf, SAMZA-561-0.patch
>
>
> We have a prototype query plan generator implemented based on Apache Calcite as a part of SAMZA-483. To be able to execute this plan as a Samza job, we need to convert this query plan to a OperatorRouter instance with corresponding operators.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)