[
https://issues.apache.org/jira/browse/SAMZA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859304#comment-15859304
]
ASF GitHub Bot commented on SAMZA-1073:
---------------------------------------
GitHub user nickpan47 opened a pull request:
https://github.com/apache/samza/pull/51
SAMZA-1073: top-level fluent API
`Initial draft of top-level fluent API for operator DAGs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/samza samza-fluent-api-v1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/51.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #51
----
commit 373048aa0a68221af5f6b5589bbe161c972b11a9
Author: Yi Pan (Data Infrastructure) <[email protected]>
Date: 2017-02-09T09:56:10Z
SAMZA-1073: top-level fluent API
`
----
> 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)
> 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)
