[
https://issues.apache.org/jira/browse/NIFI-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464027#comment-17464027
]
Ahmed Shaaban M. Abd El Megeed commented on NIFI-5149:
------------------------------------------------------
Hi Josef,
Actually I had the same workaround in my mind, but I think that doesn't deny
the fact that we need the GetSplunk processor to accept input flowfiles.
That made me think though, Do we really need an extra processor for a change
that simple ? I think we can change the GetSplunk processor to be able to take
input flowfiles or not just like InvokeHTTP processor
I understand what [~bbende] say, and I think there is no conflict in having the
processor do both roles. If time strategy is managed then it can do incremental
extractions, if it is provided then it can accept flowfiles or not.
> GetSplunk Processor should have input flow, which is currently missing
> ----------------------------------------------------------------------
>
> Key: NIFI-5149
> URL: https://issues.apache.org/jira/browse/NIFI-5149
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 1.6.0
> Reporter: Brajendra
> Priority: Critical
> Labels: getSplunk
>
> Hi Team,
> We have found there is only 'GetSplunk' processor to connect and query to
> Splunk in Apache NiFi.
> Hence, we this processor does not take any type or input.
>
> Do we have another type to Apache NiFi processor which can take parameters
> as input (details of Splunk indexes, query, instance etc.) from other
> processor?
> If not then please suggest when such type of processor can be expected in
> upcoming release?
>
> Environment: NiFi 1.5.0 and 1.6.0
> Brajendra Mishra
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
