Re: [DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Joe Witt
Regarding OpenLDAP Public License This does not appear to be listed under the approved apache licenses to use for source or binary dependencies. However, it looks like it is probably considered a variant of the BSD 3-Clause license which would be ok as category a. It would be helpful to

Re: [DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Andy LoPresto
Daniel, I think one reason that MiNiFi Java has been successful, both as a prototype and tool deployed in real environments today, is that it was able to leverage much of the existing NiFi Java codebase. This greatly reduced the "time-to-market” and allowed the development team to get working

Re: [DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Daniel Cave
For me personally, I don't see a value add of MiNiFi Java. The needs that NiFi can't address MiNiFi Java can't either, so my focus is MiNiFi C++ as that is the hole that needs fixing, again in my opinion, so that is where my MiNiFi focus is going to be. As I go through things I am sure I will

Re: [DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Aldrin Piri
Hi Daniel, Thanks for mailing and getting involved with MiNiFi! There is no inherent coupling of versions rather, as has been the custom within the NiFi community, we use, roughly, semantic versioning. As a result, our initial release of MiNiFi C++ started as 0.0.1 and since there have been

Re: [DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Daniel Cave
Having been out of touch since MiNiFi C++ got added and just getting into it, is there a reason the C++ version is trying to follow closely the MiNiFi Java version rather than just insuring connectivity with NiFi? I have not been able to find alot of details regarding the roadmap for MiNiFi C++.

[DISCUSS] MiNiFi C++ 0.1.0 Release

2016-11-22 Thread Aldrin Piri
Hey folks, There have been some nice improvements increasing stability and another step toward framework parity with its Java counterparts. There was also work done to update build tooling to provide a better foundation to tackle specific environments and flexibility in generating differing