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 2017/02/16 23:07:41 UTC

[jira] [Resolved] (SAMZA-1073) Design top-level fluent APIs operators that are capable to be deployed in multi-stage jobs

     [ https://issues.apache.org/jira/browse/SAMZA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yi Pan (Data Infrastructure) resolved SAMZA-1073.
-------------------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.13.0

> Design top-level fluent APIs operators that are capable to be deployed in multi-stage jobs
> ------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-1073
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1073
>             Project: Samza
>          Issue Type: New Feature
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Yi Pan (Data Infrastructure)
>             Fix For: 0.13.0
>
>         Attachments: SAMZA-1073operator-multi-stagejob-levelprogrammingAPI.pdf
>
>
> It would be nice to allow users to stay at logic level when using fluent API's operators, w/o concerning about physical partitions of the stream and potential grouping of operators into multiple / single Samza jobs (SAMZA-1041).
> Hence, the fluent API needs to be able to express the physical topics as boundaries between stages in the single logic DAG.
> Besides, users should be able to use fluent API to describe a logic expression at top level, not within a job or within a task.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)