[
https://issues.apache.org/jira/browse/NIFI-4985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16788826#comment-16788826
]
Sandish Kumar HN edited comment on NIFI-4985 at 3/10/19 1:39 AM:
-----------------------------------------------------------------
[~pvillard] as NIFI Kafka processor support multiple topics (", separated
topics"), proposed JIRA story can only be achieved for a single topic, as Kafka
seek method is based on specific partition. do you think it's still valuable
if we implement for a single topic?
was (Author: [email protected]):
[~pvillard] as NIFI Kafka processor support multiple topics (", separated
topics"), proposed JIRA story can only be achieved for a single topic, do you
think it's still valuable if we implement for a single topic?
> Allow users to define a specific offset when starting ConsumeKafka
> ------------------------------------------------------------------
>
> Key: NIFI-4985
> URL: https://issues.apache.org/jira/browse/NIFI-4985
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Sandish Kumar HN
> Priority: Major
>
> It'd be useful to add support for dynamic properties in ConsumeKafka set of
> processors so that users can define the offset to use when starting the
> processor. The properties could be something like:
> {noformat}
> kafka.<topic>.<partition>.offset{noformat}
> If, for a configured topic, such a property is not defined for a given
> partition, the consumer would use the auto offset property.
> If a custom offset is defined for a topic/partition, it'd be used when
> initializing the consumer by calling:
> {noformat}
> seek(TopicPartition, long){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
