You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org> on 2015/03/10 16:06:38 UTC

[jira] [Updated] (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:all-tabpanel ]

Milinda Lakmal Pathirage updated SAMZA-561:
-------------------------------------------
    Attachment: Query_Planner_SAMZA_561-0.pdf

Initial version of design document. I haven't yet figure out all the details related to planning window aggregates and joins based on Julian's latest document at https://github.com/julianhyde/incubator-calcite/blob/chi/doc/STREAM.md and Yi's window operator design document. I'll keep this document updated as I figure out aggregates and joins.

> 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
>         Attachments: Query_Planner_SAMZA_561-0.pdf
>
>
> 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)