I'm glad to see the discussion of this topic. I have nothing material to
add apart the caution that making NiFi too hard to install (it has
always been super easy--especially important for non-engineer folk) will
detract from my ability to recommend it. If it becomes a multistep
action, adding nothing more than the need to install NiFi then a few
specific NARs, that should be tolerable, however, if building is
required, it gets sticky.
I'm pretty confident that others in more decision-making roles have this
same interest at heart so, as I say, I won't contribute more to this
discussion.
Russ
On 01/12/2018 01:10 PM, Joe Witt wrote:
Team,
The NiFi convenience binary (tar.gz/zip) size has grown to 1.1GB now
in the latest release. Apache infra expanded it to 1.6GB allowance
for us but has stated this is the last time.
https://issues.apache.org/jira/browse/INFRA-15816
We need consider:
1) removing old nars/less commonly used nars/or particularly massive
nars from the assembly we distribute by default. Folks can still use
these things if they want just not from our convenience binary
2) collapsing nars with highly repeating deps
3) Getting the extension registry baked into the Flow Registry then
moving to separate releases for extension bundles. The main release
then would be just the NiFi framework.
Any other ideas ?
I'll plan to start identifying candiates for removal soon.
Thanks
Joe
