[MINOR][SS][DOCS] Adapt multiple watermark policy comment to the reality#25832
Closed
bartosz25 wants to merge 1 commit into
Closed
[MINOR][SS][DOCS] Adapt multiple watermark policy comment to the reality#25832bartosz25 wants to merge 1 commit into
bartosz25 wants to merge 1 commit into
Conversation
previous comment was true for Apache Spark prior 2.4.0. The 2.4.0 release brought multiple watermark policy and therefore stating that the 'min' is always chosen is misleading.
Member
|
Thank you for your first contribution, @bartosz25 . I updated your PR title a little. |
dongjoon-hyun
changed the title
Member
|
ok to test |
dongjoon-hyun
changed the title
Contributor
Author
|
Thank you @dongjoon-hyun |
dongjoon-hyun
approved these changes
Sep 18, 2019
dongjoon-hyun
left a comment
dongjoon-hyun
left a comment
Member
There was a problem hiding this comment.
+1, LGTM. Merged to master/branch-2.4.
This is a comment-only change and GitHub Action and Jenkins compilation test passed already.
dongjoon-hyun
pushed a commit
that referenced
this pull request
Sep 18, 2019
### What changes were proposed in this pull request? Previous comment was true for Apache Spark 2.3.0. The 2.4.0 release brought multiple watermark policy and therefore stating that the 'min' is always chosen is misleading. This PR updates the comments about multiple watermark policy. They aren't true anymore since in case of multiple watermarks, we can configure which one will be applied to the query. This change was brought with Apache Spark 2.4.0 release. ### Why are the changes needed? It introduces some confusion about the real execution of the commented code. ### Does this PR introduce any user-facing change? No. ### How was this patch tested? The tests weren't added because the change is only about the documentation level. I affirm that the contribution is my original work and that I license the work to the project under the project's open source license. Closes #25832 from bartosz25/fix_comments_multiple_watermark_policy. Authored-by: bartosz25 <bartkonieczny@yahoo.fr> Signed-off-by: Dongjoon Hyun <dhyun@apple.com> (cherry picked from commit b4b2e95) Signed-off-by: Dongjoon Hyun <dhyun@apple.com>
|
Test build #110925 has finished for PR 25832 at commit
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Previous comment was true for Apache Spark 2.3.0. The 2.4.0 release brought multiple watermark policy and therefore stating that the 'min' is always chosen is misleading.
This PR updates the comments about multiple watermark policy. They aren't true anymore since in case of multiple watermarks, we can configure which one will be applied to the query. This change was brought with Apache Spark 2.4.0 release.
Why are the changes needed?
It introduces some confusion about the real execution of the commented code.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
The tests weren't added because the change is only about the documentation level. I affirm that the contribution is my original work and that I license the work to the project under the project's open source license.