Hey Andre, Establishing another client is definitely a priority such that we can have a foundation for establishing the needed protocols to aid in working toward centralized management and command and control. With C++ we are starting from an empty repository and there is a lot of ground to cover. We've had some initial contributions but there is a lot of work to do in terms of establishing a comparable framework. I think we could maybe aim for something that provides some of the base functionality to get people engaged and tinkering. This would additionally open things up to make various parts of the entire MiNiFi data lifecycle able to be worked on in parallel and iteratively.
A proposed roadmap based on discussion we had is available [1] and would encourage folks to chime in with thoughts on that progression. [1] https://cwiki.apache.org/confluence/display/NIFI/Proposed+Roadmap On Tue, Jul 5, 2016 at 10:43 PM, Andre <[email protected]> wrote: > Aldrin, > > This is great news! > > Are there plans of releasing minifi-cpp anytime soon? > > > > On Wed, Jul 6, 2016 at 6:53 AM, Aldrin Piri <[email protected]> wrote: > > > Hey folks, > > > > We've had some nice work done on the MiNiFi Java implementation but would > > love to start putting things through their paces and extend the > community. > > To that end, I would like to tackle our first release and volunteer to > take > > the RM duties. > > > > MiNiFi has benefitted from the extensive body of work that the Apache > NiFi > > community has done and, building on that, provides another approach to > data > > collection and processing, establishing design and deploy of flows via > > declarative configuration. Currently, this is accomplished via YAML, but > > interfaces are extensible to support additional/other means and evolve as > > the community establishes a path forward. > > > > As part of maintaining a smaller footprint, those processors included are > > those located in the NiFi standard NAR to provide the core acquisition > > process. As MiNiFi continues on, we shall seek to maintain API > > compatibility between NiFi and MiNiFi as per the efforts of NIFI-1896. > If > > the base distribution of MiNiFi is not sufficient, additional NiFi > > distribution or custom NARs can be additionally loaded. > > > > There are a couple tickets in their final stages of review and after > those > > wrap up, I will look to give cover the LICENSE and NOTICE items as well > as > > augment and extend our existing NiFi release processes for any additional > > needs that may arise. > > > > For those who have not had the opportunity to scope out the intents of > > MiNiFi or could use a refresher, many of the points from the community's > > original discussion on this effort can be located on its wiki page [1]. > > Please feel free to comment and add any additional thoughts either there > or > > on JIRA [2]. > > > > Thanks! > > --Aldrin > > > > [1] https://cwiki.apache.org/confluence/display/NIFI/MiNiFi > > [2] https://issues.apache.org/jira/browse/MINIFI > > >
