[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146112#comment-15146112
]
Joseph Witt commented on NIFI-924:
----------------------------------
[[email protected]] Thank you. For a contrib like this which
essentially allows for the hosting of another framework for example it will be
really important to come out with solid documentation on the concept,
limitations, benefits, and so on. It is for example great that this allows
camel users to more readily host their flows and use the impressive array of
extensions camel already provides. However, it does not mean that the user
experience of NiFi afforded by native processors will be available for those
camel routes/extensions nor will the fine grained benefits of provenance be
available. This is in some ways similar to the support that exists for Flume.
In any case this is a great thing overall and I just want to make the point
that we need to document this well.
Also, we need to be really careful about whether we decide to include this into
the standard release of NiFi or whether we line this up as something which gets
released with the source release of NiFi but not included as part of the base
standard convenience binary. NiFi is already quite large at just over 380MB
tar.gz. So, this may be a great candidate for the registry concept we've
talked about.
Have not had a chance myself to go back through the PR again but will be happy
to do so as available.
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)
