[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146304#comment-15146304
]
Joseph Witt commented on NIFI-924:
----------------------------------
Puspendu,
Yes that is certainly true. However, classloader isolation as the Nars
provide, is an important feature.
For a case and opportunity such as this we would not want to simply merge it in
and then sort out the goals/objectives afterward. As you'll note for more
strategic and involved items we have
https://cwiki.apache.org/confluence/display/NIFI/NiFi+Feature+Proposals. What
is nice about these is it offers a chance to discuss and articulate the vision
and address the pros and cons of certain approaches. That is certainly a
recommended step for this as we need to go into this eyes wide open about how
this could be great for users. Simply referring to the impressive library of
camel extensions is not quite enough. NIFi offers a very different user
experience, framework, and overall approach for a reason. What I do not know,
and I am hoping you or others in the community will know, is the considerations
for memory usage, reliability of the data while it is within a camel route,
threading model, and more as it relates to camel. I will note that we did not
have this level of information for Flume initially either but it took several
months for that to be merged and after some great reviews/discussions and the
author understood both NIFI and Flume really well. We'll need your help to
reach that level here as well.
Thanks
Joe
> Add Camel support in NiFi
> -------------------------
>
> Key: NIFI-924
> URL: https://issues.apache.org/jira/browse/NIFI-924
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Jean-Baptiste Onofré
>
> I'm working on a NiFi Route able to leverage a Camel route (runtime routing),
> and another one being able to bootstrap a Camel route starting from Camel
> DSLs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
