[
https://issues.apache.org/jira/browse/NIFI-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499313#comment-16499313
]
Sivaprasanna Sethuraman commented on NIFI-5243:
-----------------------------------------------
[~joetrite]
Thanks for showing interest in having this feature. Few things have to be
thoroughly discussed and cleared out. The current set of List*-Fetch*
processors are all around files or other similar resources (S3 object, Azure
blob, Google Cloud objects) so the pattern makes sense there, in the sense that
the last processed file's modified time is used to keep track of the state so
that the new files or objects which are added after that will be picked up.
However in this case of listing Kafka topics, what's the objective? I don't
think the objective is to list the latest topics, right? I'm just curious on
where this approach can add value? An example scenario would certainly help me
in understanding this.
> Add ListKafkaTopics Processor
> -----------------------------
>
> Key: NIFI-5243
> URL: https://issues.apache.org/jira/browse/NIFI-5243
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Joe Trite
> Priority: Major
>
> I need to get a list of available Kakfa topics which I can filter and pass as
> input to ConsumeKafka* processors. This will provide me the ability to
> ingest Kafka messages using the same List > Fetch pattern that I currently
> use with files and tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
