[
https://issues.apache.org/jira/browse/KAFKA-17057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-17057:
------------------------------------
Description:
With KAFKA-16508 we changed the KS behavior to call the
ProductionExceptionHandler for a single special case of a potentially missing
output topic, to break an infinite retry loop.
However, this seems not to be very flexible, as users might want to retry for
some cases.
We might also consider to not calling the handler when writing into internal
topics, as those _must_ exist.
KIP-1065:
[https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627309]
was:
With KAFKA-16508 we changed the KS behavior to call the
ProductionExceptionHandler for a single special case of a potentially missing
output topic, to break an infinite retry loop.
However, this seems not to be very flexible, as users might want to retry for
some cases.
We might also consider to not calling the handler when writing into internal
topics, as those _must_ exist.
> Add "retry" option to ProductionExceptionHandler
> ------------------------------------------------
>
> Key: KAFKA-17057
> URL: https://issues.apache.org/jira/browse/KAFKA-17057
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Major
>
> With KAFKA-16508 we changed the KS behavior to call the
> ProductionExceptionHandler for a single special case of a potentially missing
> output topic, to break an infinite retry loop.
> However, this seems not to be very flexible, as users might want to retry for
> some cases.
> We might also consider to not calling the handler when writing into internal
> topics, as those _must_ exist.
> KIP-1065:
> [https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=311627309]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
