[
https://issues.apache.org/jira/browse/NIFI-924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266122#comment-15266122
]
Puspendu Banerjee commented on NIFI-924:
----------------------------------------
[~mattf] Please open a new ticket [if you want] with your concerns and let
other folks to enhance that too.
[~joewitt] please add your concern about provenance reporting feature from
inside camel and any other pain-points that you might be facing from real
customer standpoint :) (I'm still running it as demos in lab) .
[~ozhurakousky] & [~hfaouaz] If you have any concern/comment/suggestion about
this .
[~jbonofre] You as owner of the original ticket may have some vision to share.
[ Understood that you might be pretty busy with Beam :) ]
The only concern with the mentioned model will be regarding NiFi distro size,
which can again be handled via
1.dynamic classloader[ ex: groovy based] can load all dependencies as required
by camel routes '
2. and a dependency resolver is capable of downloading dependency from maven
compatible repositories if not present in classpath
> 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)
