Closed MRyanEvans closed 7 months ago
First, I assume that you've already determined you can't achieve what you're looking for by specifying the specific exception types to retry via the
exceptionTypes
annotation field?
Yes, unfortunately the exceptions that we're dealing with -- schema registry HTTP client exceptions -- are nested quite deeply and we need to inspect the exception body to determine whether it is transient or not.
Thanks for the feedback, I agree that a different error strategy would be a safer and better solution. I'll have a crack at it.
Right, I've kept the behaviour of the existing strategies as-is and have added additional strategies that will conditionally retry.
For the @since
Javadoc tags, I guessed that the next version would be 5.4.0
but I can change it as needed.
Right, I've kept the behaviour of the existing strategies as-is and have added additional strategies that will conditionally retry.
Awesome, I'll give it a proper review in the next couple days.
For the
@since
Javadoc tags, I guessed that the next version would be5.4.0
but I can change it as needed.
I believe that's correct.
Excellent, cheers. When can we expect the merge/release?
Excellent, cheers. When can we expect the merge/release?
I'll get it merged shortly.
As it's an enhancement to an existing feature, it should be included in the next Micronaut Platform minor release 4.4.0 (which will of course include a new minor release of this module). I'm not certain of the current target, but my guess would be those releases will occur within the next month or so as that's roughly the cadence we've been keeping.
@jeremyg484 You can see the target date in the projects: https://github.com/orgs/micronaut-projects/projects
We aim for March 19 for 4.4.0
Potential solution for https://github.com/micronaut-projects/micronaut-kafka/issues/947.
Adds
RETRY_CONDITIONALLY_ON_ERROR
andRETRY_CONDITIONALLY_EXPONENTIALLY_ON_ERROR
listener error stratiegies to conditionally retry messages on error.