[
https://issues.apache.org/jira/browse/KAFKA-19939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-19939:
------------------------------------
Description:
Follow up to https://issues.apache.org/jira/browse/KAFKA-19930
We should look into making the ProcessingExceptionHandler, and DLQ work for the
global thread, too.
Depending on how we do this, this might require a KIP, as we might need to add
a new producer to the global thread to support DLQ. An alternative could be, to
explicitly exclude DLQ.
For this work, we also need to make sure the restore path works, which would
read from the same global input topic, and also apply the Processor during
restoration (did we also cover this for the regular case, when we have "source
topic optimization" enabled, or is "read-only state stores" are used?
was:
Follow up to https://issues.apache.org/jira/browse/KAFKA-19930
We should look into making the ProcessingExceptionHandler, and DLQ work for the
global thread, too.
Depending on how we do this, this might require a KIP, as we might need to add
a new producer to the global thread to support DLQ.
> ProductionExceptionHandler and DLQ does not support global thread
> -----------------------------------------------------------------
>
> Key: KAFKA-19939
> URL: https://issues.apache.org/jira/browse/KAFKA-19939
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Priority: Major
>
> Follow up to https://issues.apache.org/jira/browse/KAFKA-19930
> We should look into making the ProcessingExceptionHandler, and DLQ work for
> the global thread, too.
> Depending on how we do this, this might require a KIP, as we might need to
> add a new producer to the global thread to support DLQ. An alternative could
> be, to explicitly exclude DLQ.
> For this work, we also need to make sure the restore path works, which would
> read from the same global input topic, and also apply the Processor during
> restoration (did we also cover this for the regular case, when we have
> "source topic optimization" enabled, or is "read-only state stores" are used?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
