nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre Villard <pierre.villard...@gmail.com>
Subject Re: [DISCUSS] MiNiFi C++ Initial Release - cpp-0.0.1
Date Fri, 05 Aug 2016 06:17:28 GMT
+1, awesome!

2016-08-05 6:16 GMT+02:00 Matt Burgess <mattyb149@gmail.com>:

> +1, also we need documentation on the S2S protocol so we can further
> extend the reach (Go, Python, Erlang/Elixir, etc)
>
>
> > On Aug 4, 2016, at 11:42 PM, Aldrin Piri <aldrinpiri@gmail.com> wrote:
> >
> > Hey folks,
> >
> > There's been great efforts to get an initial working implementation of
> > MiNiFi in C++.  This currently provides a great start on the core
> > functionalities that the Java equivalent provides.  Perhaps the neatest
> of
> > all these items is the C++ implementation of the Site to Site protocol
> > allowing transmission from a native instance to the NiFi we have all come
> > to use and love in a more bite-sized binary.
> >
> > To that end and to aid in making the MiNiFi effort a bit more concrete, I
> > would like to get a vote started on 0.0.1 (JIRA cpp-0.0.1) in the next
> few
> > days and would be happy to act as the RM. There are still a few issues to
> > tackle mostly tailored around documentation
> >
> > The hope is that with a Java and C++ implementation in hand there will
> be a
> > larger foundation on which people can get involved and participate.  This
> > is especially crucial as we start expanding the framework, look to
> solidify
> > APIs, and consider protocols to facilitate the design and implementation
> of
> > centralized management and bi-directional communications.
> >
> > There is still much to be done both with our MiNiFi agent implementations
> > and everything that follows.  This marks another nice milestone of
> progress
> > and will further generate a multitude of avenues for people to get
> > involved.
> >
> > Looking forward to the new possibilities and challenges ahead.
> >
> > --Aldrin
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message