You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
I want to throw errors from my controllers to Kafka's eachMessage in order to use kafkajs's retries.
Tried using a custom ExceptionFilter to rethrow the error, but found out it lead to an infinite loop of throw-catch inside RpcProxy
Describe the solution you'd like
Change RpcExceptionsHandler implementation to allow in some way to throw errors behind it
What is the motivation / use case for changing the behavior?
I understand the need to catch every exception, but this really hurts kafkajs expected behaviour, kafka worth nothing to us if we cant handle errors and retries.
The text was updated successfully, but these errors were encountered:
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
I want to throw errors from my controllers to Kafka's eachMessage in order to use kafkajs's retries.
Tried using a custom ExceptionFilter to rethrow the error, but found out it lead to an infinite loop of throw-catch inside RpcProxy
Describe the solution you'd like
Change RpcExceptionsHandler implementation to allow in some way to throw errors behind it
Teachability, documentation, adoption, migration strategy
Should be transparent.
What is the motivation / use case for changing the behavior?
I understand the need to catch every exception, but this really hurts kafkajs expected behaviour, kafka worth nothing to us if we cant handle errors and retries.
The text was updated successfully, but these errors were encountered: