[
https://issues.apache.org/jira/browse/FLINK-25690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477780#comment-17477780
]
Etienne Chauchot edited comment on FLINK-25690 at 1/18/22, 11:43 AM:
---------------------------------------------------------------------
[~chesnay] I did not know that it was on its way out.
I think we should add deprecation notice to _RetryRule_ and other classes on
their way out so that people like me could know that they are using deprecated
classes.
That being said I've already done the code because I needed it for cassandra
flakiness fixes but I can comply to what you think is best guys.
was (Author: echauchot):
[~chesnay] I did not know that it was on its way out. That being said I've
already done the code because I needed it for cassandra flakiness fixes.
> RetryRule should allow a callback to be called on exception and failure cases
> -----------------------------------------------------------------------------
>
> Key: FLINK-25690
> URL: https://issues.apache.org/jira/browse/FLINK-25690
> Project: Flink
> Issue Type: Improvement
> Reporter: Etienne Chauchot
> Assignee: Etienne Chauchot
> Priority: Major
> Labels: test
>
> RetryRule is a Flink junit rule that allows to retry tests when they
> temporary fail (either by throwing an exception or by failing an assertion)
> usually in case of load. In some cases, there is some treatment to be done
> for the test to be idempotent when retried for example cleaning of created
> data etc...
> Of course, this callback will be optional.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
