New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FLINK-15307][failover]Rename Subclasses of FailoverStrategy #10848
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit a3f83df (Tue Jan 14 01:09:34 UTC 2020) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
CI report:
Bot commandsThe @flinkbot bot supports the following commands:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this PR @chendonglin521
I left a few comments for it.
@GJL would you also take a look at this change?
@@ -59,7 +59,7 @@ | |||
/** | |||
* Tests for {@link AdaptedRestartPipelinedRegionStrategyNG}. | |||
*/ | |||
public class AdaptedRestartPipelinedRegionStrategyNGAbortPendingCheckpointsTest extends TestLogger { | |||
public class AdaptedRestartPipelinedRegionFailoverStrategyNGAbortPendingCheckpointsTest extends TestLogger { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not do this since this PR does not rename AdaptedRestartPipelinedRegionStrategyNG.
@@ -51,7 +51,7 @@ | |||
* Tests for {@link AdaptedRestartPipelinedRegionStrategyNG} failover handling when concurrent failovers happen. | |||
* There can be local+local and local+global concurrent failovers. | |||
*/ | |||
public class AdaptedRestartPipelinedRegionStrategyNGConcurrentFailoverTest extends TestLogger { | |||
public class AdaptedRestartPipelinedRegionFailoverStrategyNGConcurrentFailoverTest extends TestLogger { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's related to a legacy failover strategy AdaptedRestartPipelinedRegionStrategyNG
so do not rename it in this PR.
@@ -63,7 +63,7 @@ | |||
/** | |||
* Tests for {@link AdaptedRestartPipelinedRegionStrategyNG} failover handling. | |||
*/ | |||
public class AdaptedRestartPipelinedRegionStrategyNGFailoverTest extends TestLogger { | |||
public class AdaptedRestartPipelinedRegionFailoverStrategyNGFailoverTest extends TestLogger { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is not needed. See my other 2 comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I check carefully and modify.
// TODO the 'NO_OF_RETRIES' is useless for current RestartPipelinedRegionStrategy, | ||
// for this ContinuousFileProcessingCheckpointITCase, using RestartPipelinedRegionStrategy would result in endless running. | ||
throw new AssumptionViolatedException("ignored ContinuousFileProcessingCheckpointITCase when using RestartPipelinedRegionStrategy"); | ||
// TODO the 'NO_OF_RETRIES' is useless for current RestartPipelinedRegionFailoverStrategy, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is actually not flip. RestartPipelinedRegionStrategy
but StreamFaultToleranceTestBase#FailoverStrategy
.
I think we need to rename the enums in it as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't agree with you more. I will rename the enums
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhuzhurk Hi zhuzhu, Appreciation of your kind guidance , and I've updated it according to your comments
Thanks for addressing the comments @chendonglin521 . |
I am fine with the name changes. |
Thanks for the feedback @GJL . |
What is the purpose of the change
Subclasses of FailoverStrategy are easily confused with implementation classes of RestartStrategy
Given that the failover strategy class names are transparent to users
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: noDocumentation