Eliaaazzz opened a new pull request, #39023:
URL: https://github.com/apache/beam/pull/39023
This adds an experimental Watch transform to the Python SDK. It addresses
#21521.
Watch watches a growing set of outputs for each input element. It calls a
user poll function on an interval and emits an unbounded PCollection of input
and output pairs. Polling stops per input when the poll reports completion or
when a termination condition fires. The transform is a splittable DoFn, so each
process call performs one poll round and then self checkpoints with
defer_remainder, which keeps the polling loop durable across bundles. New
outputs are deduplicated with a stable 128 bit blake2b hash of the encoded
output, and a manual watermark estimator advances once per poll.
This is an initial minimal version intended for review and iteration. It
implements growth_of, PollResult, PollFn, the never and after_total_of
termination conditions, the growth state restriction with its coder, and the
polling splittable DoFn. It is validated end to end on the DirectRunner. The
output coder must be deterministic for dedup to hold across workers, and the
transform logs a warning when the resolved coder is not deterministic.
The following are out of scope for this initial change and are not included
here: side input poll functions, the remaining termination conditions, a
separate bounded stage for exploding large poll results, and bounded growth
state eviction.
Testing
- Unit tests for the termination conditions and for the growth state coder
round trips, including ordered completed hashes and a fixed width 16 byte hash
coder.
- Restriction tracker tests for claim, dedup, checkpoint, replay,
boundedness, and a terminal split residual for every stop reason, so a
checkpoint after a terminal poll cannot resume polling.
- DirectRunner end to end tests for single poll completion, multiple
inputs, and multi round dedup.
- Local run reports 32 tests passing and pylint at 10.00 of 10.
------------------------
Thank you for your contribution! Follow this checklist to help us
incorporate your contribution quickly and easily:
- [x] Mention the appropriate issue in your description (for example:
`addresses #123`), if applicable. This will automatically add a link to the
pull request in the issue. If you would like the issue to automatically close
on merging the pull request, comment `fixes #<ISSUE NUMBER>` instead.
- [ ] Update `CHANGES.md` with noteworthy changes.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
See the [Contributor Guide](https://beam.apache.org/contribute) for more
tips on [how to make review process
smoother](https://github.com/apache/beam/blob/master/CONTRIBUTING.md#make-the-reviewers-job-easier).
To check the build health, please visit
[https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md](https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md)
GitHub Actions Tests Status (on master branch)
------------------------------------------------------------------------------------------------
[](https://github.com/apache/beam/actions?query=workflow%3A%22Build+python+source+distribution+and+wheels%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Python+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Java+Tests%22+branch%3Amaster+event%3Aschedule)
[](https://github.com/apache/beam/actions?query=workflow%3A%22Go+tests%22+branch%3Amaster+event%3Aschedule)
See [CI.md](https://github.com/apache/beam/blob/master/CI.md) for more
information about GitHub Actions CI or the [workflows
README](https://github.com/apache/beam/blob/master/.github/workflows/README.md)
to see a list of phrases to trigger workflows.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
