GitHub user kennknowles opened a pull request:
https://github.com/apache/beam/pull/2731
[BEAM-2086] Remove TestDataflowRunner reliance on metrics in streaming
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [ ] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [ ] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf).
---
Metrics are not supported yet in Dataflow streaming.
- The Dataflow service automatically shuts down jobs when their input
watermarks reach infinity, so we don't need metrics for that.
- Counting `PAsserts` is nice but given the current architecture less of a
critical concern. And anyhow, Dataflow just doesn't support it yet!
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kennknowles/beam TestDataflowRunner
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2731.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 #2731
----
commit 4757d54bbd372b76ca44680a7b7886819db9943f
Author: Kenneth Knowles <[email protected]>
Date: 2017-04-27T00:55:29Z
Do not rely on metrics in streaming TestDataflowRunner
The Dataflow service automatically shuts down jobs when their
input watermarks reach infinity, and other functionality can be
restored when the feature is restored to the Dataflow service.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
