[
https://issues.apache.org/jira/browse/NIFI-12783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Jakupovic updated NIFI-12783:
-----------------------------------
Description:
Hi,
the Kafka producer processors do not route the FlowFiles on a timeout e.g. into
the failure connection. They are yielded in the incomming connection.
You can see the behaviour here e.g.:
[https://stackoverflow.com/questions/71460008/apache-nifi-publishkafka-timeout-exception]
I think this is a design flaw. I have a use case where messages should be
dropped after a specific configurable time. If the messages are yielded in the
incomming queue they are always published when the kafka broker are available
again. I know I can set the expiration time in secs or mins in the incomming
queue but it is not dynamically configurable because no attributes are allowed.
Best
Denis
was:
Hi,
the Kafka producer processors do not route the FlowFiles on a timeout e.g. into
the failure connection. They are yielded in the incomming connection.
You can see the behaviour here e.g.:
[https://stackoverflow.com/questions/71460008/apache-nifi-publishkafka-timeout-exception]
I think this is a design flaw. I have a use case where messages should be
dropped after a specific time. If the messages are yielded in the incomming
queue they are always published when the kafka broker are available again.
Best
Denis
> Kafka Producer Processors do not route in failure queue on timeout
> ------------------------------------------------------------------
>
> Key: NIFI-12783
> URL: https://issues.apache.org/jira/browse/NIFI-12783
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.23.2
> Reporter: Denis Jakupovic
> Priority: Major
>
> Hi,
> the Kafka producer processors do not route the FlowFiles on a timeout e.g.
> into the failure connection. They are yielded in the incomming connection.
> You can see the behaviour here e.g.:
> [https://stackoverflow.com/questions/71460008/apache-nifi-publishkafka-timeout-exception]
> I think this is a design flaw. I have a use case where messages should be
> dropped after a specific configurable time. If the messages are yielded in
> the incomming queue they are always published when the kafka broker are
> available again. I know I can set the expiration time in secs or mins in the
> incomming queue but it is not dynamically configurable because no attributes
> are allowed.
> Best
> Denis
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
