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
@loicgreffier I am thinking for deserialization this issue is corrected by this PR : #75
For production, I think we check if the exception is retriable.
BUT, linked to the issue: how to treat InvalidPidMappingException? when we have that the record is not produced. If we catch it into the production exception handler and return ProductionExceptionHandlerResponse.FAIL, the stream is restarted, a new producer id and a new transactional is assigned, and the stream re-attempt to produce. We can discuss about it during a meeting 😉 and may be open the debate on other Invalid Exception like InvalidProducerEpochException 😉
Some production error or deserialization error can be retriable.
The production error handler and the deserialization error handler should handle these errors.
The text was updated successfully, but these errors were encountered: