[
https://issues.apache.org/jira/browse/NIFI-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604529#comment-14604529
]
ASF GitHub Bot commented on NIFI-589:
-------------------------------------
Github user rdblue commented on the pull request:
https://github.com/apache/incubator-nifi/pull/51#issuecomment-116191838
> Is there any service provider construct or similar mechanism whereby we
could provide a dropdown of identified sources and sinks
I think this is primarily intended to allow people to use their current
Flume config inside of NiFi and pave the way for more seamless integration as a
next step. I would say we want to keep this as-is for compatibility (just paste
in your current config) and create processors to wrap the widely used Flume
components, like the Avro source.
> I think because channel.setSession(…) is being called as it is during the
onTrigger method this means the processor needs to run serially
Good point. Maybe we can keep a thread-local cache of the sessions and pass
an accessor to the channel instead? Then we would be able to keep parallel
execution.
> Add processors that can run Apache Flume sources/sinks
> ------------------------------------------------------
>
> Key: NIFI-589
> URL: https://issues.apache.org/jira/browse/NIFI-589
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 0.1.0
> Reporter: Joey Echeverria
> Assignee: Joey Echeverria
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)