Sounds like a great proposal. Im excited to see what you come up with.
james
14.03.2017, 19:56, "Otto Fowler" :
> RE: questions -
>
> - The archetype will produce NARs so having it with the VFSClassloader
> doesn’t work, unless
> I do an archetype without nars, but that
RE: questions -
- The archetype will produce NARs so having it with the VFSClassloader
doesn’t work, unless
I do an archetype without nars, but that would be so short lived I wouldn’t
bother.
- My goal is to do it in such a way that I could propose / submit the
changes made back to nifi ( worse
I like the direction of using NAR. The key benefits I see (there are
others, but I picked by favorites):
1. Move away from the uber jars in Storm. Granted, this should be possible
with modifications from the new Stellar classloader. My hope is that this
would allow us to stop shading the parser
I would definitely agree that moving forward we should consider something
like Nar for Stellar. I'm not seeing the need for parsers exactly.
I don't want to squash the forward thinking aspect here; we should be broad
and think about the end, ideal state. I just want to make sure we think
"The Apache NiFi NAR ‘system’ allows for the packaging and loading of java
resources with classloader isolation.
Although technically it is the Service Provider api that makes the
‘plugins’ part of the system, you can view them
together, and thus look at the NAR features as a system to create,
I like the approach. I think Nar constitutes a production-quality existing
solution meeting highly similar needs to Metron’s.
Just a ‘btw’ regarding Joe’s input that I transmitted:
- Joe made clear that he was only giving his personal opinion, since of course
no individual can speak for the