[
https://issues.apache.org/jira/browse/BEAM-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252637#comment-16252637
]
ASF GitHub Bot commented on BEAM-2899:
--------------------------------------
GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/4133
[BEAM-2899] Add a Local Java Module
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).
---
This contains utilities shared by runners which execute locally. This
is expected to be the DirectRunner and the ReferenceRunner, both of
which can utilize shared in-memory representations about the state of an
executing Pipeline.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam local_java_core
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/4133.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 #4133
----
commit d71996c014d1cb86a5991ff9c30e9abd1f9c1a89
Author: Thomas Groh <[email protected]>
Date: 2017-10-25T23:31:09Z
Add a Local Java Core Module
This contains utilities shared by runners which execute locally. This
is expected to be the DirectRunner and the ReferenceRunner, both of
which can utilize shared in-memory representations about the state of an
executing Pipeline.
commit a7bb1a2de113701ccbbef69c0f88207344adee0e
Author: Thomas Groh <[email protected]>
Date: 2017-11-09T02:39:21Z
Move StructuralKey to the local execution module
commit cb8be30c65c9a6c1d046f2b53c016e5bce23e311
Author: Thomas Groh <[email protected]>
Date: 2017-11-14T02:08:17Z
Add A TransformExecutorFactory
This creates executors provided an input bundle, a transform, a
completion callback, and a service to execute the transform on.
----
> Universal Local Runner
> ----------------------
>
> Key: BEAM-2899
> URL: https://issues.apache.org/jira/browse/BEAM-2899
> Project: Beam
> Issue Type: Improvement
> Components: runner-core
> Reporter: Henning Rohde
> Assignee: Thomas Groh
> Labels: portability
>
> To make the portability effort tractable, we should implement a Universal
> Local Runner (ULR) in Java that runs in a single server process plus docker
> containers for the SDK harness containers. It would serve multiple purposes:
> (1) A reference implementation for other runners. Ideally, any new feature
> should be implemented in the ULR first.
> (2) A fully-featured test runner for SDKs who participate in the
> portability framework. It thus complements the direct runners.
> (3) A test runner for user code that depends on or customizes the runtime
> environment. For example, a DoFn that shells out has a dependency that may be
> satisfied on the user's desktop (and thus works fine on the direct runner),
> but perhaps not by the container harness image. The ULR allows for an easy
> way to find out.
> The Java direct runner presumably has lots of pieces that can be reused.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
