[
https://issues.apache.org/jira/browse/NIFI-5243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16501851#comment-16501851
]
Sivaprasanna Sethuraman commented on NIFI-5243:
-----------------------------------------------
Since what you have explained seems to build the processors on demand i.e.
based on the topics listed, check if anything is new and create ConsumeKafka
accordingly, I would suggest you making use of the REST API service offered by
NiFi, rather than having a dedicated processor to do this (as it looks more of
a approach that targets a specific usecase and doesn't seem to benefit the
community on the whole, IMHO).
And for handling and cleaning up "test" topics. I can think of a simple
InvokeHTTP -> PutEmail. In InvokeHTTP use Kafka API. (Ex:
[http://localhost:8082/topics]).
> 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)
