Skip to content

[BEAM-8532] Output timestamp should be the inclusive, not exclusive, end of window.#9958

Merged
robertwb merged 1 commit intoapache:masterfrom
robertwb:trigger-timestamp
Nov 4, 2019
Merged

[BEAM-8532] Output timestamp should be the inclusive, not exclusive, end of window.#9958
robertwb merged 1 commit intoapache:masterfrom
robertwb:trigger-timestamp

Conversation

@robertwb
Copy link
Contributor


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang SDK Apex Dataflow Flink Gearpump Samza Spark
Go Build Status --- --- Build Status --- --- Build Status
Java Build Status Build Status Build Status Build Status
Build Status
Build Status
Build Status Build Status Build Status
Build Status
Python Build Status
Build Status
Build Status
Build Status
--- Build Status
Build Status
Build Status
Build Status
--- --- Build Status
XLang --- --- --- Build Status --- --- ---

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website
Non-portable Build Status Build Status
Build Status
Build Status Build Status
Portable --- Build Status --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

Copy link
Member

@kennknowles kennknowles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow! This seems valuable enough to cherrypick to 2.17.0 release branch, even though it is not a regression.

@robertwb
Copy link
Contributor Author

robertwb commented Nov 4, 2019

Yeah, amazing (and scary) what you can find when you add some testing.

@robertwb
Copy link
Contributor Author

robertwb commented Nov 4, 2019

Yes, I agree it's severe enough to consider cherry-picking into 2.17. @Ardagan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants