You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@samza.apache.org by xinyuiscool <gi...@git.apache.org> on 2017/03/03 22:32:09 UTC
[GitHub] samza pull request #75: SAMZA-1067: Physical execution graph and planner for...
GitHub user xinyuiscool opened a pull request:
https://github.com/apache/samza/pull/75
SAMZA-1067: Physical execution graph and planner for fluent API
Initial commit for the physical graph and plan. The commit includes:
1) Physical ProcessorGraph, where each processor represents a physical execution unit (e.g. a job in Yarn).
2) A planner does the following:
- create ProcessorGraph from StreamGraph. For this phase, the graph only contains a single node (single stage);
- figure out the partitions of intermediate topics
- create the topics
Please note currently the planner is used in the remote runner for now. Further changes/refactoring/cleanup are expected to be integrated with local runner.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xinyuiscool/samza SAMZA-1067
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/samza/pull/75.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 #75
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] samza pull request #75: SAMZA-1067: Physical execution graph and planner for...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/samza/pull/75
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---