[
https://issues.apache.org/jira/browse/BEAM-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111045#comment-16111045
]
ASF GitHub Bot commented on BEAM-2431:
--------------------------------------
GitHub user sb2nov opened a pull request:
https://github.com/apache/beam/pull/3676
[BEAM-2431] Adding the job API
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/projects/BEAM/issues/) filed for the
change (usually before you start working on it). Trivial changes like typos do
not require a JIRA issue. Your pull request should address just this issue,
without pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject
line and body.
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will be performed on your pull request automatically.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
---
R: @tgroh PTAL
This is part 1 of many for the job submission API. Currently experimental
so might evolve a bit as we make progress.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sb2nov/beam BEAM-2431-beam-job-api_1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/3676.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 #3676
----
commit b75c6c62f20282182fe923ecd7cc5edc25022f40
Author: Sourabh Bajaj <[email protected]>
Date: 2017-08-02T14:44:16Z
[BEAM-2431] Adding the job API
----
> Model Runner interactions in RPC layer for Runner API
> -----------------------------------------------------
>
> Key: BEAM-2431
> URL: https://issues.apache.org/jira/browse/BEAM-2431
> Project: Beam
> Issue Type: New Feature
> Components: beam-model-runner-api
> Reporter: Kenneth Knowles
> Assignee: Sourabh Bajaj
> Labels: beam-python-everywhere
>
> The "Runner API" today is actually just a definition of what constitutes a
> Beam pipeline. It needs to actually be a (very small) API.
> This would allow e.g. a Java-based job launcher to respond to launch requests
> and state queries from a Python-based adapter.
> The expected API would be something like a distillation of the APIs for
> PipelineRunner and PipelineResult (which is really "Job") via analyzing how
> these both look in Java and Python.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)