damccorm opened a new pull request, #22816: URL: https://github.com/apache/beam/pull/22816
This continues to grow our state support by adding bag state support. Once both this and #22815 are in, I'll add a follow up PR with an integration test. In the meantime, I tested manually by running the hacked wordcount found here - https://github.com/damccorm/beam/pull/86/files#diff-46f0bd8f9f6b541e840079960d684ba78e6513f1293b673d08faaec94d48a234 - and it produced output like: ``` ... away([]): 1 away([I]): 1 away([I I]): 1 away([I I I]): 1 away([I I I I]): 1 away([I I I I I]): 1 away([I I I I I I]): 1 away([I I I I I I I]): 1 away([I I I I I I I I]): 1 away([I I I I I I I I I]): 1 away([I I I I I I I I I I]): 1 away([I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I I I I I]): 1 away([I I I I I I I I I I I I I I I I I I I I I I I I I I I I I]): 1 injuries([]): 1 injuries([I]): 1 injuries([I I]): 1 necessities([]): 1 Be([]): 1 Be([I]): 1 Be([I I]): 1 Be([I I I]): 1 Be([I I I I]): 1 Be([I I I I I]): 1 Be([I I I I I I]): 1 Be([I I I I I I I]): 1 Be([I I I I I I I I]): 1 Be([I I I I I I I I I]): 1 Be([I I I I I I I I I I]): 1 Be([I I I I I I I I I I I]): 1 Be([I I I I I I I I I I I I]): 1 Be([I I I I I I I I I I I I I]): 1 Be([I I I I I I I I I I I I I I]): 1 Be([I I I I I I I I I I I I I I I]): 1 ... ``` Part of #22736 ------------------------ Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] [**Choose reviewer(s)**](https://beam.apache.org/contribute/#make-your-change) and mention them in a comment (`R: @username`). - [ ] 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://beam.apache.org/contribute/get-started-contributing/#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. -- 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]
