[
https://issues.apache.org/jira/browse/NIFI-8021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259776#comment-17259776
]
Mark Payne commented on NIFI-8021:
----------------------------------
I've also encountered a related bug where if we set multiple concurrent tasks
with statically defined partitions, for every message we will get N copies of
the message, where N is equal to the number of concurrent tasks.
> Allow ConsumeKafka processors to use static partition mapping
> -------------------------------------------------------------
>
> Key: NIFI-8021
> URL: https://issues.apache.org/jira/browse/NIFI-8021
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.13.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With the ConsumeKafka processors, we use the KafkaConsumer.subscribe()
> method, which is generally what is desirable. However, for a case where
> strict FIFO order per partition is critical, as may be the case with CDC use
> cases among others, we should allow users to pin a particular partition to a
> particular node. This way, even if the node is restarted or stops pulling
> data for a while, its partitions are not re-assigned, so there's no risk of
> messages being delivered out of order.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
