Details
Description
In general, KafkaProducer could throw both fatal and non-fatal errors as KafkaException, which makes the exception catching hard. Furthermore, not every single fatal exception (checked) is marked on the function signature yet as of 2.7.
We should have a general supporting strategy in long term for this matter, as whether to declare all non-fatal exceptions as wrapped KafkaException while extracting all fatal ones, or just add a flag to KafkaException indicating fatal or not, to maintain binary compatibility.
Attachments
Issue Links
- fixes
-
KAFKA-13292 InvalidPidMappingException: The producer attempted to use a producer id which is not currently assigned to its transactional id
-
- Resolved
-
- links to
1.
|
Avoid double wrapping KafkaException |
|
Open | Unassigned |
2.
|
Wrap non-fatal exception as AbortableException |
|
Open | Unassigned |
3.
|
Convert INVALID_PRODUCER_EPOCH into PRODUCER_FENCED TxnOffsetCommit |
|
Resolved | Lucas Brutschy |