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 2014/12/01 18:10:12 UTC

[jira] [Commented] (SAMZA-482) Identify the set of operators for SQL on Samza

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

Yi Pan (Data Infrastructure) commented on SAMZA-482:
----------------------------------------------------

[~bkirwi], the operators would probably become build-in libraries in Samza. I would think that it be unnecessary to add another indirect layer between existing Samza API and the operator layer. Do you have any particular use case that will benefit from that additional layer of representation?

> Identify the set of operators for SQL on Samza
> ----------------------------------------------
>
>                 Key: SAMZA-482
>                 URL: https://issues.apache.org/jira/browse/SAMZA-482
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Yi Pan (Data Infrastructure)
>            Priority: Minor
>              Labels: project
>
> This came out of a discussion between [~milinda], [~criccomini], and [~nickpan47]. We think that it will be a good idea to separate the operators layer from the high-level language layer, s.t. we can allow different languages to be built on-top-of the same set of fundamental functions (i.e. SQL-like or DSL).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)