GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/2258
[BEAM-1732] Populate Display Data in Window.Assign
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.txt).
---
This populates the diff between the input and output Windowing
Strategies as the display data of the primitive.
Certain elements are slightly changed, due to implementation details of
Windowing Strategy. All specified elements, regardless of where they
were specified, will be included in the Display Data.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam window_assign_display_data
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2258.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 #2258
----
commit fc59cd00dfab866bacd4fb12ddb8e8d5e27f6154
Author: Thomas Groh <[email protected]>
Date: 2017-03-15T23:52:48Z
Populate Display Data in Window.Assign
This populates the diff between the input and output Windowing
Strategies as the display data of the primitive.
Certain elements are slightly changed, due to implementation details of
Windowing Strategy. All specified elements, regardless of where they
were specified, will be included in the Display Data.
----
---
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.
---
