+1, binding
Tested the build and basic flow in OS X 10.11.6, CentOS 7, and on
Debian/Ubuntu Docker containers.
Hashes and signatures looked good.
LICENSE & NOTICE looked good. README will need some additional
improvements as highlighted by some of the feedback from the community.
Thanks!
On
+1 (binding) Release this package as nifi-minifi-cpp-0.1.0
Ran through the helper. Built and tested on OSX 10.10.5 and RHEL 7.2.
Did run into a bit of a hiccup when RHEL 7.2 when using the GetFile processor a
relative path wasn't working for the input directory and when I didn't specify
the
+1 (binding)
I downloaded the assets, verified all checksums and GPG signature, and built
the app. Initially encountered a problem on OS X 10.11.6 because I used
ossp-uuid library, but with Aldrin’s help was able to remove that and use
libuuid. Ran a simple GetFile demo and sent data back to a
+1 (binding) Release this package as nifi-minifi-cpp-0.1.0
A couple of notes...
- I had some initial troubles building and running on my laptop (OSX
10.10.5), but after installing lib uuid from source rather than brew
ossp-uuid, I was able to run on my laptop sending data to a regular NiFi
+1
On 2016-11-29 08:54 (-0800), Aldrin Piri wrote:
> Hello Apache NiFi Community,>
>
> I am pleased to be calling this vote for the source release of Apache
NiFi MiNiFi C++, nifi-minifi-cpp-0.1.0.>
>
> The source archive, signature, and digests can be located at:>
>
>
+1
On 2016-11-29 08:54 (-0800), Aldrin Piri wrote:
> Hello Apache NiFi Community,>
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> MiNiFi C++, nifi-minifi-cpp-0.1.0.>
>
> The source archive, signature, and digests can be located at:>
>
>
Hey Koji,
As far as I'm aware, minifi-cpp currently supports version 1 of the config
yaml (output by toolkit version 0.0.1). The toolkit outputs version 2 as
of 0.1.0 (It's not just property names, there are new NiFi features
supported such as process groups, funnels, etc). We need a way to
+1 (non-binding)
Build on RaspberryPi 2 without issue, took (30 - 40 minutes)
Running sample conf.yml written in README worked without issue
However, when I used minifi-toolkit-0.1.0 (included in MiNiFi java,
which is under voting, too right now) to convert a NiFi flow template
to conf.yml.
Hey Bryan, thanks for pointing this out.
Seems this was not updated in the docs with the transition to CMake and
libleveldb was also not captured in the run portion of requirements only in
the build. I've taken note of this and will capture these doc items in a
JIRA with any others that may
+1 (non-binding)
Notes:
I needed to install uuid-dev to build on Ubuntu (not part of README.md).
I needed to install libleveldb-dev to build (part of README.md) as well as
to run (not part of README.md) on Ubuntu.
Validated signature, hashes, build, sample flow in Docker Ubuntu container.
On
+1 (non-binding) Release this package as nifi-minifi-cpp-0.1.0
Validated signature, resulting assembly artifacts, and builds/packaging for
Ubuntu 16.10 and CentOs 7.2. I also validated a simple flow of tailing
local files and transferring data over site-to-site to NiFi.
On Tue, Nov 29, 2016 at
11 matches
Mail list logo