[
https://issues.apache.org/jira/browse/KAFKA-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172514#comment-17172514
]
Gokul Srinivas commented on KAFKA-10186:
----------------------------------------
[~mjsax] [~ableegoldman]
I've created a work-in-progress KIP page. Should I also take a pass at the
code, look at how best I can create the new exception and then add that to the
KIP as well?
[KIP-654|https://cwiki.apache.org/confluence/display/KAFKA/KIP-654%3A+Aborted+transaction+with+non-flushed+data+should+throw+a+non-fatal+exception]
> Aborting transaction with pending data should throw non-fatal exception
> -----------------------------------------------------------------------
>
> Key: KAFKA-10186
> URL: https://issues.apache.org/jira/browse/KAFKA-10186
> Project: Kafka
> Issue Type: Improvement
> Components: producer
> Reporter: Sophie Blee-Goldman
> Assignee: Gokul Srinivas
> Priority: Major
> Labels: needs-kip, newbie, newbie++
>
> Currently if you try to abort a transaction with any pending (non-flushed)
> data, the send exception is set to
> {code:java}
> KafkaException("Failing batch since transaction was aborted"){code}
> This exception type is generally considered fatal, but this is a valid state
> to be in -- the point of throwing the exception is to alert that the records
> will not be sent, not that you are in an unrecoverable error state.
> We should throw a different (possibly new) type of exception here to
> distinguish from fatal and recoverable errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
