[
https://issues.apache.org/jira/browse/NIFI-3437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15852074#comment-15852074
]
Joseph Witt commented on NIFI-3437:
-----------------------------------
[~ncarenza] That is already how that processor works. It is the group id in
that processor which determines how it will be tracked against the offset it
has consumed up to. You can stop/restart/rename the processor and have no
issues at all. You can even create a totally new and or additional processor
and if it uses the same group identifier it will be tracked as an additional
kafka consumer, assigned partitions, and its offset will be appropriately
tracked.
Are you seeing behavior that does not align to what I'm saying?
> KafkaConsumer pause/resume
> --------------------------
>
> Key: NIFI-3437
> URL: https://issues.apache.org/jira/browse/NIFI-3437
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Nicholas Carenza
> Priority: Minor
>
> Could the KafkaConsumer processor keep track of it's position so that if it
> is stopped and started again it can attempt to resume consuming from that
> position?
> If I have to restart nifi or rename the consumer processor I want to make
> sure I don't miss any messages.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
