[jira] [Commented] (SAMZA-561) Translate query plan generated by Calcite to Samza OperatorRouter

["Milinda Lakmal Pathirage (JIRA)" <ji...@apache.org>]

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

Milinda Lakmal Pathirage commented on SAMZA-561:
------------------------------------------------

I couldn't try the new operator API yet. But I'll go through the new API and the new multi-stage feature in coming weeks. I think it is time to figure out proper job configurations for queries as well as metadata related streams and relations. We can use Calcite's JSON based metadata format or plug directly into something like Schema Repository.

> 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, SAMZA-561-1.patch, SAMZA-561-2.patch, SAMZA-561-3.patch, SAMZA-561-4.patch, SAMZA-561-5.patch, SAMZA-561-6.patch, SAMZA-561-7.patch, SAMZA-561-8.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)