[
https://issues.apache.org/jira/browse/SAMZA-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230161#comment-14230161
]
Ben Kirwin commented on SAMZA-482:
----------------------------------
Sorry, I think my question was unclear -- I'm wondering whether this 'operator
layer' is meant to sit on top of the existing StreamTask API, or if it
integrates at a lower level. (Perhaps by providing another RunLoop
implementation, for example.) In other words, would the dependency graph would
look like this:
{code}
1)
operator layer -> task API
{code}
or this:
{code}
2)
operator layer -\
+-> low-level samza API
task API -------/
{code}
There are reasonable arguments for both (#1 is less invasive, #2 exposes
additional parallelism, etc.) and this is probably not the place for that
discussion -- just wondering what you had in mind.
> 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)
