[SPARK-18722][SS]Move no data rate limit from StreamExecution to ProgressReporter #16155
Conversation
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
Contributor
|
LGTM. |
|
Test build #69686 has finished for PR 16155 at commit
|
Contributor
|
Still LGTM. Merge when tests pass on the latest commit. |
|
Test build #69694 has finished for PR 16155 at commit
|
|
Test build #69700 has finished for PR 16155 at commit
|
Contributor
|
Merging to master and 2.1 |
asfgit
pushed a commit
that referenced
this pull request
Dec 6, 2016
…gressReporter ## What changes were proposed in this pull request? Move no data rate limit from StreamExecution to ProgressReporter to make `recentProgresses` and listener events consistent. ## How was this patch tested? Jenkins Author: Shixiong Zhu <shixiong@databricks.com> Closes #16155 from zsxwing/SPARK-18722. (cherry picked from commit 4af142f) Signed-off-by: Tathagata Das <tathagata.das1565@gmail.com>
robert3005
pushed a commit
to palantir/spark
that referenced
this pull request
Dec 15, 2016
…gressReporter ## What changes were proposed in this pull request? Move no data rate limit from StreamExecution to ProgressReporter to make `recentProgresses` and listener events consistent. ## How was this patch tested? Jenkins Author: Shixiong Zhu <shixiong@databricks.com> Closes apache#16155 from zsxwing/SPARK-18722.
uzadude
pushed a commit
to uzadude/spark
that referenced
this pull request
Jan 27, 2017
…gressReporter ## What changes were proposed in this pull request? Move no data rate limit from StreamExecution to ProgressReporter to make `recentProgresses` and listener events consistent. ## How was this patch tested? Jenkins Author: Shixiong Zhu <shixiong@databricks.com> Closes apache#16155 from zsxwing/SPARK-18722.
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?
Move no data rate limit from StreamExecution to ProgressReporter to make
recentProgressesand listener events consistent.How was this patch tested?
Jenkins