Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.13.0 (RC2)

[Marc Parisi]

+1 (binding)

Simple test capturing WEL sending to NiFi. Verified build on u22 as well,
verifying sigs and hashes.

Thanks,
Marc

On Wed, Dec 7, 2022 at 9:56 PM Marton Szasz  wrote:

> +1 (binding)
>
> - Followed the release helper guide steps, everything was in good order.
> - Tested build on both ubuntu 22.04 / GCC 11 and windows 10, with a
> wide range of extensions. Couldn't build on Arch Linux / GCC 11
> because of some weird local toolchain issue that only happens on my
> desktop. Also failed on Ubuntu/Clang due to MINIFICPP-2005 (fixed on
> main), but I don't think either of these are blockers.
> - I saw the failure of PutTCPTests, but that is a known issue of the
> test (MINIFICPP-2003, fixed on main), and not a bug in PutTCP.
> - Tested with CWEL -> InvokeHTTP (win)  // ListenHTTP -> LogAttribute
> (linux). It worked fine.
>
> Thanks for RMing!
>
> Marton
>
> On Wed, 7 Dec 2022 at 11:33, Martin Zink  wrote:
> >
> > +1 (non-binding)
> >
> > -Verified signature, hashes and git commit hash
> > -Built it from source with all extensions on Ubuntu 22.04
> > -Verified the new PutTCP and ListenTCP processors with two agents
> > communicating with each other
> >
> >
> > Thanks,
> > Martin
> >
> > On Mon, Dec 5, 2022 at 3:41 PM Gábor Gyimesi 
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > - Verified that binaries are no longer in the source archive
> > > - Verified signature, hashes and git commit hash
> > > - Built RC2 core and all extensions (excluding Tensorflow) with GCC
> 11.3 on
> > > Ubuntu 22.04
> > > - Ran all unit, integration and docker system tests
> > > - Verified contents of README.md, NOTICE, and LICENSE files
> > > - Verified built binary with simple flows having TailFile, PutFile,
> > > GenerateFlowFile, LogAttribute processors and communication through
> > > InvokeHTTP processor with NiFi's ListenHTTP processor
> > > - Verified Prometheus metrics reporting with built binary and
> Prometheus
> > > 2.35.0
> > >
> > > Thanks,
> > > Gabor
> > >
> > > On Mon, 5 Dec 2022 at 15:00, Ferenc Gerlits 
> wrote:
> > >
> > > > On Mon, Dec 5, 2022 at 2:29 PM John McGinn wrote:
> > > >
> > > > >  Just a note, but the issues closed/resolved list is inaccessible
> to
> > > the
> > > > > public. Not sure if it is meant to be that way or not.
> > > > >
> > > > > The release notes link right below it is accessible though.
> > > > >
> > > > >  Thanks for raising this!  It seems to be some weirdness in Jira.
> We
> > > may
> > > > have to use the simpler "tickets closed in this release" page:
> > > >
> > > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12351771
> > > > in future release emails -- that one seems to be accessible by
> anonymous
> > > > users.
> > > >
> > > > Thanks,
> > > > Ferenc
> > > >
> > >
>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.13.0 (RC1)

[Marc Parisi]

+1 binding.

Typical build I do with docker builds on a U22 base. Followed release
guide, confirmed sigs and hashes, and ran my prototypical flows which
include NiFi WEC -> MiNiFi -> Kafka . Didn't notice any issues with Readme
+ NOTICE or LICENSE files

Great work team!

Thanks,
Marc

On Thu, Dec 1, 2022 at 1:30 PM Jeremy Dyer  wrote:

> +1 (binding)
>
> verified source, build from source on U22.04, verified functioning docker
> builds, and confirmed valid SHAs
>
> On Thu, Dec 1, 2022 at 10:16 AM Gábor Gyimesi  wrote:
>
> > +1 (non-binding)
> >
> > - verified signature and hashes of source tar.gz file
> > - verified git commit hash
> > - built RC core and all extensions (excluding Tensorflow) with GCC 11.3
> on
> > Ubuntu 22.04
> > - ran all unit, integration and docker system tests
> > - verified contents of README.md, NOTICE, and LICENSE files
> > - verified
> >
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/nifi-minifi-cpp-0.13.0-bin-linux.tar.gz
> > binary with simple flows having TailFile, GetFile, LogAttribute
> processors
> > and communication through InvokeHTTP processor with NiFi's ListenHTTP
> > processor
> > - verified Prometheus metrics reporting with built binary and Prometheus
> > 2.35.0
> >
> > Thanks,
> > Gabor
> >
> > On Wed, 30 Nov 2022 at 11:58, Ferenc Gerlits 
> wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > MiNiFi C++ 0.13.0.
> > >
> > > The source tarball, the binary build, plus signatures and digests can
> be
> > > found at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/
> > >
> > > The Git tag is minifi-cpp-0.13.0-RC1
> > > The Git commit ID is 4389b9ac05e43e1dbf908e9014787d07c8a9cd05
> > >
> > >
> >
> https://github.com/apache/nifi-minifi-cpp/commit/4389b9ac05e43e1dbf908e9014787d07c8a9cd05
> > >
> > > Checksums of nifi-minifi-cpp-0.13.0-source.tar.gz:
> > > SHA256:
> 9cbc37cb841dbd2b53412ded7ba59cd571181b659f647b9d35c3f3ac985337c1
> > > SHA512:
> > >
> > >
> >
> 3a69ef1894e4fdc2b2e4d7cd77f46debd86c52a70cfd1a7a76445ae976cfe12bd176cfad3a6aacda2a01aa2ff5810faf2e3d3a8e8ff0de5e460ae19f63db
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/fgerlits.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 85 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/projects/MINIFICPP/versions/12351771
> > >
> > > Release note highlights can be found here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.13.0
> > >
> > > The vote will be open for 72 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-minifi-cpp-0.13.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.12.0 (RC1)

[Marc Parisi]

+1

verified sigs and hashes.

Ran a simple flow, starting, stopping, and changing flow with c2 protocol.

Everything looks good. Great stuff!

Thanks,
Marc



On Tue, May 24, 2022 at 9:56 AM Martin Zink  wrote:

> Good idea, I've renamed the convenience binary
>
> On Tue, May 24, 2022 at 2:54 PM Marton Szasz  wrote:
>
> > +1 (binding)
> >
> > Ran through the release helper guide. Tested the convenience binaries
> > with a RPG to the NiFi release candidate, then InvokeHTTP to another
> > MiNiFi C++ RC agent that I've built myself.
> >
> > I would rename the convenience binary package from
> > nifi-minifi-cpp-0.12.0-bin-centos.tar.gz to
> > nifi-minifi-cpp-0.12.0-bin-linux.tar.gz before finishing the release,
> > since it works on basically all major linux distros, even though it's
> > built on CentOS. We did the same with 0.11.0.
> >
> > Thanks!
> >
> > On Mon, 23 May 2022 at 13:28, Ferenc Gerlits 
> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > I have
> > > * verified the checksums and signatures
> > > * compared the contents of the source tarball to the
> > minifi-cpp-0.12.0-RC1
> > > tag in git
> > > * ran the binary with a simple GenerateFlowFile -> LogAttribute flow,
> > with
> > > heartbeat logging on
> > > * connected to C2
> > >
> > > Everything worked correctly.
> > >
> > > Thanks,
> > > Ferenc
> >
>

Re: [DISCUSS] MiNiFi C++ 0.12.0 release

[Marc Parisi]

Really awesome work from a great team so I think a release is in order as
well. +1

On Tue, May 17, 2022 at 5:48 AM Gábor Gyimesi  wrote:

> +1
>
> On Tue, 17 May 2022 at 11:30, Pierre Villard 
> wrote:
>
> > +1
> >
> > Le mar. 17 mai 2022 à 10:02, Ádám Markovics  a
> > écrit :
> >
> > > Hi,
> > > I also think it's time for a new release.
> > > Regards,
> > >
> > > Ádám
> > >
> > > On Mon, May 16, 2022 at 5:32 PM Marton Szasz 
> wrote:
> > >
> > > > I agree that it's time for a new release, thanks for RM'ing Martin.
> > > >
> > > > I have these two issues that I think would be nice to include in the
> > > > release:
> > > > 1. MINIFICPP-1828 fix InvokeHTTP Attributes to Send
> > > > https://github.com/apache/nifi-minifi-cpp/pull/1331
> > > > This is a bug that is severe enough that I would prefer to wait for
> > > > the fix to get merged before the release.
> > > > 2. MINIFICPP-1744: Add FetchGCSObject, DeleteGCSObject, ListGCSBucket
> > > > https://github.com/apache/nifi-minifi-cpp/pull/1297
> > > > This would be a nice addition to complete the GCS extension. Not
> > > > necessarily required for the release, but nice to have IMO. I'll try
> > > > to post a second review today or tomorrow.
> > > >
> > > >
> > > >
> > > > On Mon, 16 May 2022 at 14:57, Arpad Boda  wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On Mon, May 16, 2022 at 4:12 PM Joe Witt 
> wrote:
> > > > >
> > > > > > Certainly more than enough there!  Thanks Martin
> > > > > >
> > > > > > On Mon, May 16, 2022 at 7:06 AM Martin Zink <
> martinz...@apache.org
> > >
> > > > wrote:
> > > > > >
> > > > > > > Hi community,
> > > > > > >
> > > > > > > I'd like to initiate a discussion about the next release of
> > MiNiFi
> > > > C++.
> > > > > > The
> > > > > > > last release was five months ago, and there have been many new
> > > > features,
> > > > > > > bug fixes and stability improvements committed to the
> development
> > > > branch
> > > > > > > since. (~110 commits)
> > > > > > > I would be happy to take on RM duties for this release.
> > > > > > >
> > > > > > > New features since the 0.11.0 release:
> > > > > > > - new processors:
> > > > > > >* DeleteAzureBlobStorage
> > > > > > >* FetchAzureBlobStorage
> > > > > > >* FetchAzureDataLakeStorage
> > > > > > >* ListAzureBlobStorage
> > > > > > >* ListAzureDataLakeStorage
> > > > > > >* PutGCSObject
> > > > > > >* ProcFsMonitor
> > > > > > >* PutUDP
> > > > > > >* FetchFile
> > > > > > >* ListFile
> > > > > > >* PutSplunkHTTP
> > > > > > >* QuerySplunkIndexingStatus
> > > > > > >
> > > > > > > - Log collection from Kubernetes
> > > > > > > - improved support for Lua processors
> > > > > > > - platform independent ListenSyslog
> > > > > > > - property update over C2 protocol
> > > > > > >
> > > > > > > The core API is still not mature enough to be able to commit to
> > it,
> > > > so
> > > > > > > in line with previous discussions I suggest releasing it as
> > 0.12.0.
> > > > > > >
> > > > > > > Do you agree it is time for a new release? Are there any
> blockers
> > > > that we
> > > > > > > should definitely include in this release?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Martin
> > > > > > >
> > > > > >
> > > >
> > >
> >
>

Jira contributor access

[Marc]

Hello,

I would like to request Jira contributor access.
My Username is nerdfunk

Many thanks
Marc

Re: [RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.11.0

[Marc Parisi]

Thanks Marton. Sorry about that Adam!

On Mon, Dec 13, 2021 at 8:40 AM Marton Szasz  wrote:

> For the record, there were actually 5 +1 (binding) votes and 5 +1
> (non-binding) votes.
>
> I'm assuming the miscategorized vote was from Marc, who didn't specify
> the kind of vote in the email, but he is a member of the PMC [1], so
> his vote counts as binding. [2]
>
> Thanks,
> Marton
>
> [1] https://nifi.apache.org/people.html
> [2] https://www.apache.org/foundation/voting.html#binding-votes
>
> On Sat, 11 Dec 2021 at 16:08, Adam Debreceni 
> wrote:
> >
> > Apache NiFi Community,
> >
> > I am pleased to announce that the 0.11.0 release of Apache NiFi MiNiFi
> C++
> > passes with
> >   4 +1 (binding) votes
> >   6 +1 (non-binding) votes
> >   0 0 votes
> >   0 -1 votes
> >
> > Thanks to all who helped make this release possible.
> >
> > Here is the PMC vote thread:
> > https://lists.apache.org/thread/sktrv50h5wvpcffv6sdkh04jk32c8y0k
>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.11.0 RC2

[Marc Parisi]

+1 verified sigs and hashes and ran some test flows from a local cluster
gathering log data sending to nifi via site to site.

Works great!

On Wed, Dec 8, 2021 at 6:51 AM Ádám Markovics  wrote:

> +1 (non-binding)
> Verified and built on Ubuntu 20.04. Ran tests and also ran a simple
> (GetFile-PutFile) flow.
> Regards,
>
> Ádám
>
> On Mon, Dec 6, 2021 at 12:06 PM Adam Debreceni 
> wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > MiNiFi C++ 0.11.0.
> >
> > The source tarball, the binary build, plus signatures and digests can be
> > found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.11.0/
> >
> > The Git tag is minifi-cpp-0.11.0-RC2
> > The Git commit ID is 0553df446aefb395b34c1e4e2b5ced31f07a4e04
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=0553df446aefb395b34c1e4e2b5ced31f07a4e04
> >
> > Checksums of nifi-minifi-cpp-0.11.0-source.tar.gz:
> > SHA256: 98e161436f2ae1b9eacf27493fe3420891aa5e4e70c20216ec186c5e23c2c11d
> > SHA512:
> >
> >
> 8e968d9d58ea793d1f6f064374c07ac0ef296c2fd895941ea74c879e06fc95c48100fd9c2d28bc2bc5c523c8ad229a77a5626f8311c038aeb87d8fd4324dfe0e
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/adebreceni.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 86 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/projects/MINIFICPP/versions/12350247
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.11.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-minifi-cpp-0.11.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [DISCUSS] The future of (Mi)NiFi Command and Control (C2)

[Marc Parisi]

" This would align it more to the way NiFi works as
well, allowing C2 to be used for flow control and metadata exchange
rather than process control."

This particularly caught my eye and is something that makes sense from an
evolutionary perspective.

I've previously viewed command and control as a mechanism to control the
agent processes and their flows.

>From an operational perspective, I think that agent process control would
be nice to have (if not a necessity for some ); however, if C2 is scoped to
metadata and flow control at least -- through the MVP or permanently --
then the conversation is simpler and I think your proposal is great.

Thanks for the additional insight, Matt.

Thanks,
Marc





On Thu, Nov 18, 2021 at 4:37 PM Matt Burgess  wrote:

> Marc,
>
> That's a great point and reminds me that I missed two whole sections
> of the proposal: 1) The refactor of minifi-bootstrap, and 2) the
> standardization of serialized flow control to VersionedFlowSnapshot
> (i.e. JSON not XML or YAML).
>
> 1) Currently it's the bootstrap process that reaches out to the C2
> server and handles the commands such as UPDATE and RESTART. In fact,
> UPDATE updates the flow on-disk and RESTART then kills and restarts
> the MiNiFi process.  I think with the time that's passed since its
> inception, it has kind of gotten bloated and has taken on capabilities
> probably best left to a separate module, since those things make it
> inconsistent with the way NiFi bootstrap works . In that vein I'd
> propose (at some point, not necessarily MVP but that'd be great) that
> we standardize the bootstraps as much as possible, and put all the C2
> stuff into the C2 modules (i.e. the C2 Client in the case of
> minifi-bootstrap). I vaguely alluded to that when I said the C2 client
> would need access to the internal objects, but that glossed WAY over
> the actual implication, which is that the C2 client module will be the
> thing talking to the C2 server to handle all the C2 messages including
> UPDATE, and I think RESTART might be replaced with RELOAD or absorbed
> into UPDATE, but happy to discuss that as well.
>
> If there are issues such as updating an agent/instance with
> configuration properties, I anticipate a new proposal and design to
> cover that, but I invite current C2 Server users to jump in here
> please. As it stands I believe we haven't implemented enough of the C2
> capabilities to be affected, unless the C2 server's flow update file
> includes configurable property updates. Otherwise I would think just a
> flow update would suffice, and could be done without restarting the
> process itself. This would align it more to the way NiFi works as
> well, allowing C2 to be used for flow control and metadata exchange
> rather than process control.
>
> 2) IIRC, the "config.yml' approach came from two use cases, to be able
> to update the agent process/configuration itself and to make it easier
> to "design" a flow by having more user-friendly names for the various
> configuration and component properties without a UI designer. These
> days, the minifi-toolkit allows the user to convert a flow from
> flow.xml.gz to a config.yml, and I'm aware of at least one vendor
> product for flow design & publish via a GUI. Between the
> aforementioned lack of a need to update the agent process, and ongoing
> work [1] to standardize the flow definition for NiFi, Registry,
> Stateless, etc. to VersionedFlowSnapshot, I think MiNiFi should follow
> suit. I can't speak to the C++ side of things but perhaps those more
> familiar with that project can weigh in.
>
> My original email turned out to be more focused on the MVP products,
> but these additional aspects (as well as any others the community
> would like to offer) should be discussed too. If these are not
> necessary for MVP, perhaps we can get the work going on the API and
> MVP and continue the discussions on the Wiki and/or mailing list as
> folks want to contribute the extra goodies :)
>
> Thanks,
> Matt
>
> [1] https://issues.apache.org/jira/browse/NIFI-9069
>
> On Thu, Nov 18, 2021 at 4:07 PM Marc Parisi  wrote:
> >
> > Hi Matt,
> >
> > I think this is great. I like the MVP set of features.
> >
> > Considering use cases and potential maintenance needs, are there thoughts
> > on including RESTART in the MVP for cases where agent UPDATES may be
> > blocked for whatever reason ( I/O, agent problems, etc )?
> >
> > Does the risk of the RESTART verb being somewhat nebulous outweigh any
> > benefits?
> >
> > Again, great stuff!
> >
> > Thanks,
> > Marc
> >
> >
> > On Thu, Nov 18, 2021 at 2:20 PM Matt B

Re: [DISCUSS] The future of (Mi)NiFi Command and Control (C2)

[Marc Parisi]

Hi Matt,

I think this is great. I like the MVP set of features.

Considering use cases and potential maintenance needs, are there thoughts
on including RESTART in the MVP for cases where agent UPDATES may be
blocked for whatever reason ( I/O, agent problems, etc )?

Does the risk of the RESTART verb being somewhat nebulous outweigh any
benefits?

Again, great stuff!

Thanks,
Marc


On Thu, Nov 18, 2021 at 2:20 PM Matt Burgess  wrote:

> Hello all,
>
> I'd like to start a discussion about the current and future Command
> and Control (C2) capabilities in terms of the NiFi/MiNiFi Java
> codebase. The current implementation[1] is IMO not a pure reference
> implementation of the C2 spec [2]. It has fairly limited capability
> and uses the PullHttpChangeIngestor for the agent to ask for flow
> updates, which makes any bidirectional communication difficult. Rather
> than try to build out from what we currently have, I propose a new
> implementation (deprecating and eventually removing the old one) that
> is more generic, extensible, etc. This would include the following
> options:
>
> - Renaming of the minifi-c2 modules and perhaps the release artifacts,
> updating the documentation accordingly
> - Creation of a top-level "c2" or "nifi-c2" module that includes an
> API module, assembly, NAR, implementation, services bundle, etc. as
> needed
> - Adding/deleting/changing/using properties related to C2 configuration
> - Changing the common runtime/loading code to look for a C2 client
> implementation and instantiate that at startup, configuring it with
> the appropriate properties and injecting the objects needed for C2
> capabilities
> - Implementing a new C2 server that supports more of the C2 spec, and
> making adding more of the commands easier going forward
>
> I propose the Minimum Viable Product (MVP) C2 Client would have the
> following capabilities:
> - A "Manifest Reporter" that can either push a manifest (a document
> containing all the agent/instance capabilities such as available
> processors and their metadata, e.g.) and/or respond to a DESCRIBE
> MANIFEST request (see [2])
> - A "Heartbeat Reporter" to send HEARTBEAT messages and also to reply
> with ACKNOWLEDGEMENT messages and dispatching any commands such as
> UPDATE
> - The Heartbeat Reporter is analogous to the PullHttpChangeIngestor in
> the old system, but is much more capable
> - Supports HTTPS
>
> I propose the MVP C2 Server would have the following capabilities:
> - Handles manifest messages (push and/or pull) aka DESCRIBE MANIFEST
> - Handles the HEARTBEAT / UPDATE / ACK exchange, perhaps initially
> using the same approach as the old C2 system (loading the flow from a
> file for the UPDATE command) but would be extensible/configurable
> - Supports HTTPS
>
> This should give us not only feature parity with the old C2 system,
> but also presents a framework to build out the rest of the C2 design
> and add other capabilities. I should note that this proposal is not
> specific to MiNiFi Java. It should aim to align and use the same
> protocol(s) as MiNiFi C++ [3], and should allow us to perhaps add C2
> capabilities to NiFi itself in the future. We could track the proposal
> and progress at [4] as I believe that's what the page is intended for.
>
> I'd like to hear your thoughts on these proposals, and I'm happy to
> answer any questions or clarify as necessary. Also as this proceeds
> I'm happy to write up any Jira epics/cases/etc. and do the initial
> project structure and API setup work so others can dig in.
>
> Regards,
> Matt
>
> [1] https://github.com/apache/nifi/blob/main/minifi/minifi-c2/README.md
> [2] https://cwiki.apache.org/confluence/display/MINIFI/C2+Design
> [3] https://github.com/apache/nifi-minifi-cpp/blob/main/C2.md
> [4]
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177048430&flashId=624428108
>

Re: Using nifi in separated networks

[Marc]

Hi Daniel,

we tested two different diodes (two different manufacturer) for a longer time. 
Both diodes count the UDP packets and log any loss. Additionally we are using 
hashes to detect any form of content errors. We have tested the two diodes for 
over a year and have not seen any packet loss during this time. Both diodes 
were shipped as appliances - the manufacturer therefore knows exactly the 
hardware. 

This is also the reason why I initially decided against using a reed-solomon 
codes (or OpenRQ as another example). The effort seems greater than the 
benefit. But maybe I'll have more time to look at this later. Especially 
because I want to implement a diode based on nifi and therefore I don't know 
the hardware used.

If you are interested in a very reliable diode then another concept would be 
interesting for you. A German manufacturer uses a L4 Microkernel (similar to 
the seL4 microkernel) to prevent data being sent back. Only acks without 
payload are allowed. This works like a charm and is very reliable.

Thanks again for your interest in my work. I appreciate that.

Marc

> Am 03.08.2021 um 12:33 schrieb Daniel Chaffelson :
> 
> This is a very interesting area of integration investigation Marc, thank
> you for sharing your work!
> 
> I looked into this a little after conversations with folks in security
> applications, and I wonder if you investigated approaches to tracking and
> reporting/handling packet loss and error rates in this?
> The interest was in reasoning about loss rates, and the completeness of
> received data - something with a simple merge>put>diode>get>unpack would
> not manage I think.
> 
> I was looking at Longhair <https://github.com/catid/longhair>, and similar
> reed-solomon approaches, as a method of breaking down arbitrary files and
> transmitting for reconstitution over diodes that may have lossy behavior in
> Field scenarios.
> I also looked a little into transmitting manifests for downstream
> reconciliation, but this unravelled to be more complex an operation than
> would suit a pure NiFi implementation, so I started on the path of
> Kafka/Flink as a streaming-reconciliation service but quickly realised i
> was creating a monster without commercial interest :)
> Both approaches are easier for fewer larger files than millions of tiny
> messages in terms of practicality, and if you had very reliable diode
> transmission the overhead of ecc/reconciliation may not be worthwhile.
> Other implementations I had seen (like ZeroMQ radio/dish or blindFTP)
> seemed to talk about provable delivery as a potential requirement, but I
> only found the more simplistic 'my network is reliable and any packet loss
> is negligible anyway' approaches. I suspect the implementations of these
> more robust approaches are reserved for commercial offerings...
> 
> Anyway, I appreciate that you may not be able to share more details on
> this, but you reminded me of enjoying the investigation when I looked at it
> so I thought I'd say thanks for that.
> 
> On Tue, Aug 3, 2021 at 2:55 AM Phil H  wrote:
> 
>> Adam, that's true, although if your data size is larger than network
>> MTU there can be some disconnect there.
>> 
>> Connection per flow file is pretty slow for sustained high traffic
>> flows though (can't recall the establishment times off the top of my
>> head, but they are non-trivial).
>> 
>> On Tue, Aug 3, 2021 at 8:39 AM Adam Taft  wrote:
>>> 
>>> Just spitballing a little here. If you set the configuration of the
>> PutTCP
>>> processor property "Connection per Flowfile" to 'true' and you leave the
>>> "Outgoing Message Delimiter" as blank (none), then I don't think you have
>>> the delimiter problem that you both are describing. I could be wrong
>> though?
>>> 
>>> I would consider it a bug if you couldn't send a "raw"
>> connection-oriented
>>> object over PutTCP.  With that processor, the goal would be to: a) open a
>>> socket, b) dump whatever binary you have prepared over it, c) close the
>>> socket to signal completion of transfer. If PutTCP doesn't work this way
>>> (byte-for-byte), it should probably be flagged as a bug (its original
>>> intention was exactly this use case).
>>> 
>>> That being said, I still think custom FlowFile serialization might be
>>> something that is outside of the concern of the transport. I personally
>>> think serializing/deserializing is a different concern from transport.
>>> Arguably, sometimes the semantics of the transport protocol requires you
>> to
>>> prepare the message itself in a protocol ac

Re: Using nifi in separated networks

[Marc]

Hi Adam,

more or less it is a ‚merge', puttcp, listentcp and unpack. I hope that I am 
not wrong but the nifi ListenTCP processor uses a delimiter (\n as default?). 
If you are transferring binary data the processor splits the flow into 
‚pieces'. And the attributes are not transferred to the destination.

But your idea describes what the processor is doing.

1. It converts the attributes to a json string
2. It transfers the json string and the payload (there is a header that tells 
the destination how long the json header and how long the payload is)
3. The Listener gets the flow and decodes the header (to get the size of the 
json header and the payload)
4. It writes the payload to a flow
5. It converts the json string and sets the attributes to the flow 

If you do not want to transfer attributes you can configure a different 
decoder. In this case you can just ‚nectat‘ a binary file to nifi.

The UDP version is far more complex. There must be a counter to tell the 
destination what part of the flow file was received (even in a diode 
environment packets are not received in the right order!). And you must be 
fast, very fast. It is a multithreaded architecture because one thread cannot 
receive, decode, and write a gigabit per second. I used the disruptor library. 
Receive a packet in one thread, decode it in another thread. A third thread 
gets the packet and write the content in the right order to a flow.

I am still learning (and I am not a professional software developer). If I did 
something wrong or oversaw something please tell me.

Marc 

> Am 02.08.2021 um 22:01 schrieb Adam Taft :
> 
> Marc,
> 
> How would this differ from a more generic use of the existing processors,
> PutTCP/ListentTCP and PutUDP/ListenUDP?  I'm not sure what value is being
> added above these existing processors, but I'm sure I'm missing something.
> 
> There's already an ability to serialize flowfiles via MergeContent. And
> there's the deserialize side in UnpackContent. So a dataflow that looks
> like the following would seem a reasonable approach to the problem:
> 
> MergeContent -> PutTCP -> {diode} -> ListentTCP -> UnpackContent
> 
> I'm actually very interested in this topic, having a project that has a use
> case for a "diode". So I'm legitimately asking here, not trying to derail
> your work.
> 
> Thanks in advance,
> 
> Adam
> 
> On Sun, Aug 1, 2021 at 12:26 PM Marc  wrote:
> 
>> Greetings,
>> 
>> there are companies and organizations that strictly separate their
>> networks for security reasons. Such companies often use diodes to achieve
>> this. But of course they still have to exchange data between the networks
>> (eg. transfer data from ‚low‘ to ‚high‘). There are at least two kinds of
>> diodes. Some hardware-based ones only use one fiber optic to send data (UDP
>> based). Others use TCP, but prevent sending in the reverse direction.
>> 
>> Nifi is an amazing tool that allows data to be transferred between two
>> separate networks in a very flexible but also secure way. I have
>> implemented two processors. The first one ‚merges‘ the attributes and the
>> content of a flowfile and sends it to the destination. The second one
>> listens on a TCP port, splits attributes and content and creates a new
>> flowfile containing all attributes of the origin flow. You can send the
>> flow without attributes as well. In this case you can easily netcat a
>> binary file to Nifi.
>> 
>> These two processors are useful if you do NOT have a bidirectional
>> communication between two NiFi instances and therefore the site-2-site
>> mechanism or http(s) cannot be used.
>> 
>> We have been using these processors for a longer period of time (exactly
>> the version for 1.13.2) and would like to share these processors with
>> others. So the question to you all is: Is someone interested in these
>> processors or is this use case too special?
>> 
>> The current source code can be found on GitHub. (
>> https://github.com/nerdfunk-net/diode/ <
>> https://github.com/nerdfunk-net/diode/>)
>> 
>> I have also implemented a UDP based version of the processor. Due to the
>> nature of UDP, this is more complex and these processors are now being
>> tested.
>> 
>> Best regards
>> Marc

Re: Using nifi in separated networks

[Marc]

Hi,

no errors can be detected on the sender side (even the nic will not detect if 
the other side is down or not). If a UDP packet is lost, the receiver side will 
detect and log it. There are diodes that are using an archive. If any 
transmission is lost you can easily resend the data manually. 

Practically one proceeds as follows:
 - know your hardware very (very) well. Know how many packets can be sent 
without loss (that is most important).
 - there is only one process that sends data; No overload (congestion) may be 
generated
 - counters are used to detect packet loss (some diodes use something like ecc)

I know diodes that transfer millions of data without any loss. It is not so 
difficult as it sounds. But of course there is always the possibility of a 
packet loss without recognizing it immediately. It is always a tradeoff between 
security and convenience. 

Using two diodes always means having two separate Nifi systems. We do generate 
a unique ID that is always part of the flow (like the uuid). This ID is 
transferred across all systems. All logs contain this ID. So you see the flow 
across the network border. 

We use nifi to synchronize a lot of data across separated networks. And I don't 
know of any system that can do this better.

Regards
Marc


> Am 01.08.2021 um 23:15 schrieb Phil H :
> 
> That is interesting stuff - out of interest, if it was sent over that UDP
> diode, how would you know whether or not it got to the other side? I
> haven’t looked into the site-to-site functionality much yet but I assume it
> maintains the providence info?
> 
> On Mon, 2 Aug 2021 at 04:26, Marc  <mailto:n...@nerdfunk.net>> wrote:
> 
>> Greetings,
>> 
>> there are companies and organizations that strictly separate their
>> networks for security reasons. Such companies often use diodes to achieve
>> this. But of course they still have to exchange data between the networks
>> (eg. transfer data from ‚low‘ to ‚high‘). There are at least two kinds of
>> diodes. Some hardware-based ones only use one fiber optic to send data (UDP
>> based). Others use TCP, but prevent sending in the reverse direction.
>> 
>> Nifi is an amazing tool that allows data to be transferred between two
>> separate networks in a very flexible but also secure way. I have
>> implemented two processors. The first one ‚merges‘ the attributes and the
>> content of a flowfile and sends it to the destination. The second one
>> listens on a TCP port, splits attributes and content and creates a new
>> flowfile containing all attributes of the origin flow. You can send the
>> flow without attributes as well. In this case you can easily netcat a
>> binary file to Nifi.
>> 
>> These two processors are useful if you do NOT have a bidirectional
>> communication between two NiFi instances and therefore the site-2-site
>> mechanism or http(s) cannot be used.
>> 
>> We have been using these processors for a longer period of time (exactly
>> the version for 1.13.2) and would like to share these processors with
>> others. So the question to you all is: Is someone interested in these
>> processors or is this use case too special?
>> 
>> The current source code can be found on GitHub. (
>> https://github.com/nerdfunk-net/diode/ 
>> <https://github.com/nerdfunk-net/diode/> <
>> https://github.com/nerdfunk-net/diode/ 
>> <https://github.com/nerdfunk-net/diode/>>)
>> 
>> I have also implemented a UDP based version of the processor. Due to the
>> nature of UDP, this is more complex and these processors are now being
>> tested.
>> 
>> Best regards
>> Marc

Using nifi in separated networks

[Marc]

Greetings,

there are companies and organizations that strictly separate their networks for 
security reasons. Such companies often use diodes to achieve this. But of 
course they still have to exchange data between the networks (eg. transfer data 
from ‚low‘ to ‚high‘). There are at least two kinds of diodes. Some 
hardware-based ones only use one fiber optic to send data (UDP based). Others 
use TCP, but prevent sending in the reverse direction.

Nifi is an amazing tool that allows data to be transferred between two separate 
networks in a very flexible but also secure way. I have implemented two 
processors. The first one ‚merges‘ the attributes and the content of a flowfile 
and sends it to the destination. The second one listens on a TCP port, splits 
attributes and content and creates a new flowfile containing all attributes of 
the origin flow. You can send the flow without attributes as well. In this case 
you can easily netcat a binary file to Nifi.

These two processors are useful if you do NOT have a bidirectional 
communication between two NiFi instances and therefore the site-2-site 
mechanism or http(s) cannot be used.

We have been using these processors for a longer period of time (exactly the 
version for 1.13.2) and would like to share these processors with others. So 
the question to you all is: Is someone interested in these processors or is 
this use case too special?

The current source code can be found on GitHub. 
(https://github.com/nerdfunk-net/diode/ 
<https://github.com/nerdfunk-net/diode/>)

I have also implemented a UDP based version of the processor. Due to the nature 
of UDP, this is more complex and these processors are now being tested.

Best regards
Marc

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.9.0 (RC1)

[Marc Parisi]

+1

Verified sigs and hashes

Built on PopOS ( based-off of U20.04 ). I haven't tried this release on my
ARM platforms, but will try as soon as I can.
Ran basic flow pulling log data (TailFile) and sending to an Apache NiFi
node via SiteToSite.

I think the work done in 0.9.0 has been great and applaud those that have
put work into it.

I will try to take a look at the JNI package. If an issue was created feel
free to ping me on it.


Thanks,
Marc

On Wed, Feb 17, 2021 at 5:38 AM Pierre Villard 
wrote:

> +1 binding
>
> Verified checksums and signature.
> Built on Ubuntu 20.04.
> Tested GenerateFlowFile -> MergeContent -> InvokeHTTP
>
> Thanks,
> Pierre
>
> Le mer. 17 févr. 2021 à 14:24, Gábor Gyimesi  a
> écrit :
>
> > +1 (non-binding)
> >
> > Verified checksums and signature.
> > Built on Ubuntu 20.04 with Kafka, Coap, SFTP and AWS extensions.
> > Executed tests.
> > Tested a simple flow with C2 server.
> >
> > BR,
> > Gabor
> >
> > On Tue, 16 Feb 2021 at 23:54, Arpad Boda  wrote:
> >
> > > +1 (binding)
> > >
> > > Verified hashes and signature.
> > > Built and executed tests both on Debian 10 and Win 10.
> > > Started agent, connected to C2 server, designed simple flow.
> > >
> > > Cheers,
> > > Arpad
> > >
> > > On Tue, Feb 16, 2021 at 4:57 PM Ferenc Gerlits
> > >  wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Verified hashes and the signature on the source bundle.  Suggestion:
> > the
> > > > format of the hash file could be changed to " *" so
> > one
> > > > can run eg. 'sha256 -c ...'.
> > > > Built on (a Docker container running) Ubuntu 20.04, enabling
> everything
> > > > except
> > > > * TensorFlow, because I could not find an Ubuntu package for
> > > libtensorflow;
> > > > * and JNI -- this built without error, but then I had to disable it
> > > because
> > > > it caused a runtime error at startup.  I don't think this is a
> > > showstopper.
> > > > Ran the binary using a simple InvokeHTTP -> LogAttribute flow yaml
> > > config;
> > > > it worked as expected.
> > > >
> > > > Thanks,
> > > > Ferenc
> > > >
> > > > On Tue, Feb 16, 2021 at 4:23 PM Adam Debreceni <
> adebrec...@apache.org>
> > > > wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Verified checksums and signatures.
> > > > > Built on Windows 10 with kafka. Can connect to c2 server and
> receive
> > > > > updates.
> > > > > Can process windows event logs in various JSON formats and send
> them
> > to
> > > > > kafka
> > > > > through SSL, in a multi broker setup.
> > > > >
> > > > > On Tue, Feb 16, 2021 at 9:50 AM Marton Szasz 
> > > wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I am pleased to be calling this vote for the source release of
> > Apache
> > > > > > NiFi MiNiFi C++ 0.9.0
> > > > > >
> > > > > > The source tarball, including signatures, digests, etc. can be
> > found
> > > > at:
> > > > > >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.9.0/
> > > > > >
> > > > > > The Git tag is minifi-cpp-0.9.0
> > > > > > The Git commit ID is a52faa5136031abfcc321a44fbcd954ee0f73764
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=a52faa5136031abfcc321a44fbcd954ee0f73764
> > > > > >
> > > > > > Checksums of nifi-minifi-cpp-0.9.0-source.tar.gz:
> > > > > > SHA256:
> > > > 40fa837c86707e3bf0e8f0aca5bc279d813205cd326edf809e7785af7282
> > > > > > SHA512:
> > > > > >
> > > > >
> > > >
> > >
> >
> 43490ba823d7846c3cc323a634d756a0a33828f5c82a623d19b77c4ddfe3248aa524245ee2c47a7fd04f41c3611758972307e221fa0a254e0aa5831c4f9b03f2
> > > > > >
> > > > > > Release artifacts are signed with the following key:
> > > > > > https://people.apache.org/keys/committer/szaszm.asc
> > > > > >
> > > > > > KEYS file available here:
> > > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > > >
> > > > > > 200 issues were closed/resolved for this release:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12345444
> > > > > >
> > > > > > Release note highlights can be found here:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.9.0
> > > > > >
> > > > > > The vote will be open for 72 hours.
> > > > > > Please download the release candidate and evaluate the necessary
> > > items
> > > > > > including checking hashes, signatures, build from source, and
> test.
> > > > > > Then please vote:
> > > > > >
> > > > > > [ ] +1 Release this package as nifi-minifi-cpp-0.9.0
> > > > > > [ ] +0 no opinion
> > > > > > [ ] -1 Do not release this package because...
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release Apache NiFi 1.13.0 (rc4)

[Marc Parisi]

+1
- Verified sigs and hashes
- Built on PopOS w/ java 8 && 11
- Tested with basic flow sending data to various devices w/ Secured
transport
- Tested secured w/ secured nifi reg.

Thanks,
Marc

On Fri, Feb 12, 2021 at 2:56 PM Andrew Lim 
wrote:

> +1 (binding)
>
> -Tested secure NiFi with secure NiFi Registry 0.8.0
> -Ran basic flows successfully
> -Tested basic versioned flow functionality
> -Reviewed and tested Core UI fixes and Documentation updates
>
> Drew
>
> > On Feb 10, 2021, at 11:37 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.13.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1178
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.0/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.13.0-RC4
> > The Git commit ID is 3bc6a122091214b33eee17a270163d7ca26e2a0c
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=3bc6a122091214b33eee17a270163d7ca26e2a0c
> >
> > Checksums of nifi-1.13.0-source-release.zip:
> > SHA256: 95efe5db38e973c9f4062a7b2c95fdc5dad31d7c5e1d36ce1776b9b227c89b9c
> > SHA512:
> >
> d7dd9e851341ebd605784142a7861935f6f814bc612499013456a15713bc9119e426df8f26445c260bdb25cbfc21822cf0d44985bf372a065c9d8597953a3c4a
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 260 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348700
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test. Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-1.13.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: Confluence write access

[Marc Parisi]

Marton,

Sorry for the late reply, I gave you perms to add and update the spaces.
Please let me know if you have any issues.

Thanks,
Marc

On Mon, Feb 8, 2021 at 10:27 AM Marton Szasz  wrote:

> Hi,
>
> I would like to ask for write access to the MiNiFi space on Confluence to
> create release notes, update outdated parts of the release guide, etc.
>
> Thanks,
> Marton
>

Re: [VOTE] Release Apache NiFi 1.12.0

[Marc Parisi]

+1 (binding )

Ran through helper guide with clean build env . Ran flows that ingest and
query Apache hbase and accumulo from a 10 VM secured cluster in my local
environment with jdk11.

Thanks,
Marc


On Sat, Aug 15, 2020, 7:11 AM Kotaro Terada  wrote:

> +1 (non-binding)
>
> Verified signatures and hashes.
> Built an RPM package with OpenJDK 11.0.8 on CentOS 7.8.
> Set up a 3-node cluster.
> Tested several flows.
>
> Thanks,
> Kotaro
>
>
> On Sat, Aug 15, 2020 at 5:09 PM Joey Frazee  .invalid>
> wrote:
>
> > +1 (non-binding)
> >
> > Verified commit id, checksums, and signatures
> > Successfully built and ran tests on Linux with Java 1.8.0_252 and Java
> > 11.0.7 2020-04-14 and on macOS with Java 11.0.6 2020-01-14 LTS
> > Ran data flows on standalone and cluster
> > Verified JMS improvements, InvokeHTTP changes, and Azure integration in
> > commercial and gov regions
> >
> > -joey
> > On Aug 14, 2020, 1:31 PM -0700, Robert Fellows ,
> > wrote:
> > > + 1 (non-binding)
> > >
> > > Ran through the release helper, verified checksums and sigs.
> > > Full build with java 11
> > > Verified basic app usage/functionality.
> > >
> > >
> > >
> > > On Fri, Aug 14, 2020 at 4:04 PM Muazma Zahid  wrote:
> > >
> > > > +1 (non-binding)
> > > > Ran through the release helper. Deployed a 10 node cluster on Azure
> and
> > > > verified the functionality of new ADLS processors with a standard
> flow.
> > > > Looks good to me.
> > > >
> > > > Thanks,
> > > > Muazma
> > > >
> > > > On Fri, Aug 14, 2020 at 12:45 PM Andrew Lim <
> > andrewlim.apa...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1 (binding)
> > > > >
> > > > > -Ran full clean install on OS X (Catalina 10.15.2)
> > > > > -Tested secure NiFi with secure NiFi Registry 0.7.0
> > > > > -Ran basic flows successfully; tested basic versioned flow
> > functionality
> > > > > -Reviewed documentation updates. Lots of a great additions in this
> > > > release!
> > > > > -Reviewed core UI fixes and improvements. Verified that controller
> > > > > services are searchable [1], but filed a Jira for the navigation to
> > the
> > > > > controller service being broken [2].
> > > > >
> > > > > Drew
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/NIFI-5925 <
> > > > > https://issues.apache.org/jira/browse/NIFI-5925>
> > > > > [2] https://issues.apache.org/jira/browse/NIFI-7742 <
> > > > > https://issues.apache.org/jira/browse/NIFI-7742>
> > > > >
> > > > > > On Aug 13, 2020, at 4:31 PM, Joe Witt 
> wrote:
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I am pleased to be calling this vote for the source release of
> > Apache
> > > > > NiFi
> > > > > > 1.12.0.
> > > > > >
> > > > > > The source zip, including signatures, digests, etc. can be found
> > at:
> > > > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1165
> > > > > >
> > > > > > The source being voted upon and the convenience binaries can be
> > found
> > > > at:
> > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.0/
> > > > > >
> > > > > > A helpful reminder on how the release candidate verification
> > process
> > > > > works:
> > > > > >
> > > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > > > >
> > > > > > The Git tag is nifi-1.12.0-RC1
> > > > > > The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> > > > > >
> > > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> > > > > >
> > > > > > Checksums of nifi-1.12.0-source-release.zip:
> > > > > > SHA256:
> > > > a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> > > > > > SHA512:
>

Re: [VOTE] Release Apache NiFi Registry 0.7.0

[Marc Parisi]

+1 binding

Verified sigs and hashes

Built and run on Linux LXC (Java 11) w/ Secured Apache NiFi built and run
in the same container. All looked good

Perused L&N and it looked good.

Thanks,
Marc

On Fri, Jul 17, 2020 at 5:48 PM Peter Turcsanyi 
wrote:

> +1 (non-binding)
>
> - verified signatures and checksums
> - built with Java 8 (empty local maven repo, OS: Ubuntu 18)
> - run NiFi Registry and connected to it from NiFi 1.11.4 (unsecure),
> performed some tests
> - download the convenience binary and tested a few things on it too
>
> Thanks,
> Peter
>
> On Fri, Jul 17, 2020 at 7:20 PM Marton Szasz  wrote:
>
> > +1 (non-binding)
> >
> > Followed the verification guide, migrated a test deployment using
> > GitFlowPersistenceProvider from 0.6.0, then tested MiNiFi C++ C2 flow
> > update using the new registry version.
> >
> > Thanks,
> > Marton
> >
> > On Fri, 17 Jul 2020 at 18:36, Mark Payne  wrote:
> >
> > > +1 (binding)
> > >
> > > Verified full build with contrib check, deployed and performed some
> > tests,
> > > verifying that the FlowFiles concurrency and outbound policy was
> properly
> > > stored and retrieved.
> > >
> > > Thanks
> > > -Mark
> > >
> > >
> > > > On Jul 17, 2020, at 11:55 AM, Pierre Villard <
> > > pierre.villard...@gmail.com> wrote:
> > > >
> > > > +1 (binding)
> > > >
> > > > * went through the usual release verification steps (signatures,
> build,
> > > > contrib check, licenses)
> > > > * deployed a local NR 0.7.0 instance with a single local NiFi
> > > > 1.12.0-SNAPSHOT (non secure)
> > > >
> > > > Thanks Bryan for taking care of this!
> > > >
> > > > Le ven. 17 juil. 2020 à 17:46, Matt Burgess  a
> > > écrit :
> > > >
> > > >> +1 (binding), verified hashes and commit ID, tested a few things on
> an
> > > >> unsecured instance. Thanks for RM'ing Bryan!
> > > >>
> > > >> On Wed, Jul 15, 2020 at 11:32 AM Bryan Bende 
> > wrote:
> > > >>>
> > > >>> Hello,
> > > >>>
> > > >>> I am pleased to be calling this vote for the source release of
> Apache
> > > >> NiFi
> > > >>> Registry 0.7.0.
> > > >>>
> > > >>> The source zip, including signatures, digests, etc. can be found
> at:
> > > >>>
> > https://repository.apache.org/content/repositories/orgapachenifi-1161
> > > >>>
> > > >>> The source being voted upon and the convenience binaries can be
> found
> > > at:
> > > >>>
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.0/
> > > >>>
> > > >>> A helpful reminder on how the release candidate verification
> process
> > > >> works:
> > > >>>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > >>>
> > > >>> The Git tag is nifi-registry-0.7.0-RC1
> > > >>> The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac
> > > >>>
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac
> > > >>>
> > > >>> Checksums of nifi-registry-0.7.0-source-release.zip:
> > > >>> SHA256:
> > > acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8
> > > >>> SHA512:
> > > >>>
> > > >>
> > >
> >
> 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683
> > > >>>
> > > >>> Release artifacts are signed with the following key:
> > > >>> https://people.apache.org/keys/committer/bbende.asc
> > > >>>
> > > >>> KEYS file available here:
> > > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >>>
> > > >>> 19 issues were closed/resolved for this release:
> > > >>>
> > > >>
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12346077
> > > >>>
> > > >>> Release note highlights can be found here:
> > > >>>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.0
> > > >>>
> > > >>> The vote will be open for 72 hours.
> > > >>> Please download the release candidate and evaluate the necessary
> > items
> > > >>> including checking hashes, signatures, build from source, and test.
> > > Then
> > > >>> please vote:
> > > >>>
> > > >>> [ ] +1 Release this package as nifi-registry-0.7.0
> > > >>> [ ] +0 no opinion
> > > >>> [ ] -1 Do not release this package because...
> > > >>
> > >
> > >
> >
>

Re: [discuss]Release MiNiFi-CPP 0.8.0

[Marc Parisi]

+1 to 0.8.0. Been keeping up with changes and I think the progress is
great.

In my opinion the breaking changes are long coming and probably would be
appreciated by the community.

Arpad are you thinking of going to 1.x? You're discussing 0.8, but is there
any reason to not jump to 1.x after that?

Thanks,
Marc

On Wed, Jul 15, 2020 at 10:12 AM Joe Witt  wrote:

> Arpad
>
> Yep makes sense. Frankly the 0. versioning gives the flexibility to do
> these breaking changes during this stage of the lifecycle.
>
> Thanks
>
> On Wed, Jul 15, 2020 at 7:06 AM Arpad Boda  wrote:
>
> > Hey,
> >
> > Quite a lot of time has passed since the last release and also a lot of
> > improvements and bug fixes have been made (Memleaks fixed, new
> threadpool,
> > some new processors, etc), so I think it's time for a new release.
> >
> > Another important aspect would be the release of the current state of the
> > source before introducing some breaking changes - which seems to be
> > necessary at this point.
> >
> > What do you think?
> >
> > Thanks, regards,
> > Arpad
> >
>

Re: [ANNOUNCE] New NiFi PMC member Drew Lim

[Marc Parisi]

Congrats Drew!

On Fri, May 29, 2020 at 10:14 PM Andrew Lim 
wrote:

> Thanks everyone! Excited about NiFi's future with you all!
>
> -Drew
>
> On Fri, May 29, 2020 at 5:24 PM Mike Thomsen 
> wrote:
>
> > Congratulations!
> >
> > On Fri, May 29, 2020 at 4:56 PM Peter Turcsanyi 
> > wrote:
> >
> > > Congrats Drew!
> > >
> > > On Fri, May 29, 2020 at 10:50 PM Joe Witt  wrote:
> > >
> > > > congrats Drew!  youve been helping make nifi easier to use for a long
> > > time
> > > >
> > > > On Fri, May 29, 2020 at 1:32 PM Andy LoPresto 
> > > > wrote:
> > > >
> > > > > Congratulations and welcome Drew. The work you’ve done makes the
> > > > community
> > > > > so much more accessible and drives user success everywhere. I refer
> > to
> > > > your
> > > > > work myself all the time. Looking forward for your continued
> > > > contributions.
> > > > >
> > > > > Andy LoPresto
> > > > > alopre...@apache.org
> > > > > alopresto.apa...@gmail.com
> > > > > He/Him
> > > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > > >
> > > > > > On May 29, 2020, at 1:18 PM, Pierre Villard <
> > > > pierre.villard...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > Awesome Drew! Congrats! Your work is super useful for all the
> > > > community,
> > > > > > well deserved!
> > > > > >
> > > > > > Le ven. 29 mai 2020 à 21:55, Tony Kurc  a
> écrit
> > :
> > > > > >
> > > > > >> NiFi Community,
> > > > > >>
> > > > > >> On behalf of the Apache NiFi PMC, I am pleased to announce that
> > Drew
> > > > Lim
> > > > > >> has accepted the PMC's invitation to join the Apache NiFi PMC.
> > > > > >>
> > > > > >> Drew has been doing an amazing job for several years making NiFi
> > > more
> > > > > >> approachable and usable. He's contributed to almost every part
> of
> > > > NiFi;
> > > > > >> going over and beyond to improve documentation and usability.
> > > > > >>
> > > > > >> Please join us in congratulating and welcoming Drew to the
> Apache
> > > NiFi
> > > > > PMC.
> > > > > >>
> > > > > >> Congratulations Drew!
> > > > > >>
> > > > > >> Tony
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Arpad Boda

[Marc Parisi]

Congrats Arpad!

On Fri, May 29, 2020 at 5:25 PM Mike Thomsen  wrote:

> Congratulations!
>
> On Fri, May 29, 2020 at 4:55 PM Peter Turcsanyi 
> wrote:
>
> > Congrats Arpad!
> >
> > On Fri, May 29, 2020 at 10:46 PM Joe Witt  wrote:
> >
> > > Congrats and thank you!
> > >
> > > On Fri, May 29, 2020 at 1:32 PM Andy LoPresto 
> > > wrote:
> > >
> > > > Congratulations Arpad, very well deserved and excited to see your
> > > > continued contributions. Pálinka on me next time I’m in Budapest.
> > > >
> > > > Andy LoPresto
> > > > alopre...@apache.org
> > > > alopresto.apa...@gmail.com
> > > > He/Him
> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > >
> > > > > On May 29, 2020, at 1:16 PM, Pierre Villard <
> > > pierre.villard...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Congrats Arpad, very well deserved!
> > > > >
> > > > > Le ven. 29 mai 2020 à 21:48, Tony Kurc  a écrit
> :
> > > > >
> > > > >> NiFi Community,
> > > > >>
> > > > >> On behalf of the Apache NiFi PMC, I am pleased to announce that
> > Arpad
> > > > Boda
> > > > >> has accepted the PMC's invitation to join the Apache NiFi PMC.
> > > > >>
> > > > >> In addition to being a regular code contributor and engaged
> > community
> > > > >> member with the project, (especially MiNiFi C++!) for quite some
> > time,
> > > > >> Arpad has done the arduous task of being a release manager for
> both
> > > NiFi
> > > > >> Registry and MiNiFi C++, which is a challenging and detail
> oriented
> > > > task.
> > > > >>
> > > > >> Please join us in congratulating and welcoming Arpad to the Apache
> > > NiFi
> > > > >> PMC.
> > > > >>
> > > > >> Congratulations Arpad!
> > > > >>
> > > > >> Tony
> > > > >>
> > > >
> > > >
> > >
> >
>

Re: MiNiFi commits for h2o

[Marc Parisi]

Hey Joe,

I was trying to advocate for H2O-3 as a way to resolve this. I think I was
responding too tersely and jumping around between tasks so I've created a
follow on https://issues.apache.org/jira/browse/MINIFICPP-1214 to clarify.
We can follow from there and anyone monitoring this thread should do the
same so we're good from all concerned parties.

Thanks,
Marc



On Mon, May 4, 2020 at 12:38 PM Joe Witt  wrote:

> Yep got ya.  I'm talking about lines like
>
>
> https://github.com/apache/nifi-minifi-cpp/commit/6e5f96518764df7791519c0ee625a94a207ddc69#diff-fa43d8bfc508fc5db1c2a320e3d03cb5R33
>
> Does that seem fine to you?
>
> On Mon, May 4, 2020 at 12:29 PM Marc Parisi  wrote:
>
> > Hey Joe,
> >
> > "Yeah for the three/commit James replied on in that link - i dont see how
> > we
> > can keep those.  They import from something that I doubt very much is
> > compatible with ALv2/ASF guidelines."
> >
> > Sorry for confusing things but my statement was referring to the MiNiFi
> C++
> > Python processors that don't import as java would. I've asked the
> original
> > author to chime in here so that he can comment on the MiNiFi C++
> > processors, especially on whether or not he feels the processors should
> > stay and the other concerns raised. I'll continue to monitor this and
> > create those follow up tickets when I am able to.
> >
> > Thanks,
> > Marc
> >
> > On Mon, May 4, 2020 at 12:13 PM Joe Witt  wrote:
> >
> > > Yeah for the three/commit James replied on in that link - i dont see
> how
> > we
> > > can keep those.  They import from something that I doubt very much is
> > > compatible with ALv2/ASF guidelines.
> > >
> > > On Mon, May 4, 2020 at 12:01 PM Marc Parisi  wrote:
> > >
> > > > Afternoon Joe,
> > > >
> > > > "So in the case of minificpp we are certain there is no L&N concern
> > > > regarding either our source OR convenience binary?"
> > > >
> > > > I believe that to be the case; however, per
> > > > https://github.com/apache/nifi/pull/4242#issuecomment-622655276 I
> > think
> > > > that maybe this is moot and the author can convert those processors
> in
> > > > MiNiFI to use that open source python lib. I'm not sure if he's on
> this
> > > > chain so I will follow up on the MiNiFi tickets to ensure that is the
> > > case
> > > > when I am able to log in again ( have to fix some account issue ).
> > > >
> > > > "Lastly, why are the JIRAs still open if this is merged?  Can you
> > please
> > > > close them and assign to the proper fix version if these are 'done'?"
> > > >
> > > > Sorry, when I am able to log in ( account issue ) and make the above
> > > > comment I will close the tx. I would prefer the fix be a follow on so
> > > this
> > > > is all tracked. The ticket fell off the radar ( as did the account
> > issue,
> > > > to be frank ), so when that is resolved I will take these actions.
> You
> > > know
> > > > me Joe, I'm like a dog who sees a squirrel, but I've put a note on my
> > > > laptop to serve as a reminder.
> > > >
> > > > Thanks,
> > > > Marc
> > > >
> > > > On Mon, May 4, 2020 at 11:49 AM Joe Witt  wrote:
> > > >
> > > > > Marc
> > > > >
> > > > > I'm not opposed to it staying if there is zero license issue.  I
> only
> > > > > mentioned the maintenance as a 'additional thing to consider' -
> that
> > is
> > > > > more of a discussion item.  L&N isn't discussion - it is hard rule.
> > > > >
> > > > > Ok so in the minificpp case you're saying "there is no source or
> > binary
> > > > > dependency (that we'd package)" that isn't entirely ALv2/ASF
> > compatible
> > > > and
> > > > > so if people want to use this they can do so by adding in the 'h2o'
> > > bits
> > > > at
> > > > > their own effort, right?  In this line of thinking I still don't
> love
> > > it
> > > > > but it is arguably not a lot different that our components which
> talk
> > > to
> > > > > services you have to have a paid or otherwise agreement with like
> > Cloud
> > > > > services offering by AW

Re: MiNiFi commits for h2o

[Marc Parisi]

Hey Joe,

"Yeah for the three/commit James replied on in that link - i dont see how we
can keep those.  They import from something that I doubt very much is
compatible with ALv2/ASF guidelines."

Sorry for confusing things but my statement was referring to the MiNiFi C++
Python processors that don't import as java would. I've asked the original
author to chime in here so that he can comment on the MiNiFi C++
processors, especially on whether or not he feels the processors should
stay and the other concerns raised. I'll continue to monitor this and
create those follow up tickets when I am able to.

Thanks,
Marc

On Mon, May 4, 2020 at 12:13 PM Joe Witt  wrote:

> Yeah for the three/commit James replied on in that link - i dont see how we
> can keep those.  They import from something that I doubt very much is
> compatible with ALv2/ASF guidelines.
>
> On Mon, May 4, 2020 at 12:01 PM Marc Parisi  wrote:
>
> > Afternoon Joe,
> >
> > "So in the case of minificpp we are certain there is no L&N concern
> > regarding either our source OR convenience binary?"
> >
> > I believe that to be the case; however, per
> > https://github.com/apache/nifi/pull/4242#issuecomment-622655276 I think
> > that maybe this is moot and the author can convert those processors in
> > MiNiFI to use that open source python lib. I'm not sure if he's on this
> > chain so I will follow up on the MiNiFi tickets to ensure that is the
> case
> > when I am able to log in again ( have to fix some account issue ).
> >
> > "Lastly, why are the JIRAs still open if this is merged?  Can you please
> > close them and assign to the proper fix version if these are 'done'?"
> >
> > Sorry, when I am able to log in ( account issue ) and make the above
> > comment I will close the tx. I would prefer the fix be a follow on so
> this
> > is all tracked. The ticket fell off the radar ( as did the account issue,
> > to be frank ), so when that is resolved I will take these actions. You
> know
> > me Joe, I'm like a dog who sees a squirrel, but I've put a note on my
> > laptop to serve as a reminder.
> >
> > Thanks,
> > Marc
> >
> > On Mon, May 4, 2020 at 11:49 AM Joe Witt  wrote:
> >
> > > Marc
> > >
> > > I'm not opposed to it staying if there is zero license issue.  I only
> > > mentioned the maintenance as a 'additional thing to consider' - that is
> > > more of a discussion item.  L&N isn't discussion - it is hard rule.
> > >
> > > Ok so in the minificpp case you're saying "there is no source or binary
> > > dependency (that we'd package)" that isn't entirely ALv2/ASF compatible
> > and
> > > so if people want to use this they can do so by adding in the 'h2o'
> bits
> > at
> > > their own effort, right?  In this line of thinking I still don't love
> it
> > > but it is arguably not a lot different that our components which talk
> to
> > > services you have to have a paid or otherwise agreement with like Cloud
> > > services offering by AWS, Azure, GCP, etc..
> > >
> > > So in the case of minificpp we are certain there is no L&N concern
> > > regarding either our source OR convenience binary?
> > >
> > > Lastly, why are the JIRAs still open if this is merged?  Can you please
> > > close them and assign to the proper fix version if these are 'done'?
> > >
> > > Thanks
> > >
> > > On Mon, May 4, 2020 at 11:46 AM Marc Parisi 
> wrote:
> > >
> > > > "We should find a way for vendors to offer extension points like this
> > > > without having to take on the burden of maintenance. How can we
> > possibly
> > > do
> > > > this well?  We're learning this lesson the hard way in NiFi itself
> and
> > > this
> > > > is why the registry is being formulated."
> > > >
> > > > I think there is a fine line when walking vendor tie-in. Having the
> > > > registry allows for an arm's length agreement with the Apache
> > community.
> > > I
> > > > know others will disagree but my opinion is that extension points
> that
> > > > don't introduce licensing concerns from libraries should be fair game
> > but
> > > > the fact that a paid product requires a license for that code to be
> > > useful
> > > > should not be a non-starter -- if that makes sense. I believe I
> stated,
> > > &

Re: MiNiFi commits for h2o

[Marc Parisi]

Afternoon Joe,

"So in the case of minificpp we are certain there is no L&N concern
regarding either our source OR convenience binary?"

I believe that to be the case; however, per
https://github.com/apache/nifi/pull/4242#issuecomment-622655276 I think
that maybe this is moot and the author can convert those processors in
MiNiFI to use that open source python lib. I'm not sure if he's on this
chain so I will follow up on the MiNiFi tickets to ensure that is the case
when I am able to log in again ( have to fix some account issue ).

"Lastly, why are the JIRAs still open if this is merged?  Can you please
close them and assign to the proper fix version if these are 'done'?"

Sorry, when I am able to log in ( account issue ) and make the above
comment I will close the tx. I would prefer the fix be a follow on so this
is all tracked. The ticket fell off the radar ( as did the account issue,
to be frank ), so when that is resolved I will take these actions. You know
me Joe, I'm like a dog who sees a squirrel, but I've put a note on my
laptop to serve as a reminder.

Thanks,
Marc

On Mon, May 4, 2020 at 11:49 AM Joe Witt  wrote:

> Marc
>
> I'm not opposed to it staying if there is zero license issue.  I only
> mentioned the maintenance as a 'additional thing to consider' - that is
> more of a discussion item.  L&N isn't discussion - it is hard rule.
>
> Ok so in the minificpp case you're saying "there is no source or binary
> dependency (that we'd package)" that isn't entirely ALv2/ASF compatible and
> so if people want to use this they can do so by adding in the 'h2o' bits at
> their own effort, right?  In this line of thinking I still don't love it
> but it is arguably not a lot different that our components which talk to
> services you have to have a paid or otherwise agreement with like Cloud
> services offering by AWS, Azure, GCP, etc..
>
> So in the case of minificpp we are certain there is no L&N concern
> regarding either our source OR convenience binary?
>
> Lastly, why are the JIRAs still open if this is merged?  Can you please
> close them and assign to the proper fix version if these are 'done'?
>
> Thanks
>
> On Mon, May 4, 2020 at 11:46 AM Marc Parisi  wrote:
>
> > "We should find a way for vendors to offer extension points like this
> > without having to take on the burden of maintenance. How can we possibly
> do
> > this well?  We're learning this lesson the hard way in NiFi itself and
> this
> > is why the registry is being formulated."
> >
> > I think there is a fine line when walking vendor tie-in. Having the
> > registry allows for an arm's length agreement with the Apache community.
> I
> > know others will disagree but my opinion is that extension points that
> > don't introduce licensing concerns from libraries should be fair game but
> > the fact that a paid product requires a license for that code to be
> useful
> > should not be a non-starter -- if that makes sense. I believe I stated,
> "I
> > don't have a strong argument" as I don't really have a strong opinion (
> and
> > certainly can be wrong too ) -- so I'm interested in hearing others in
> > regards to this.
> >
> >
> >
> > On Mon, May 4, 2020 at 11:38 AM Marc Parisi  wrote:
> >
> > > Hi Joe,
> > >
> > > When merging I did not use the NiFi processors to test as I already
> have
> > > tooling around H20 driven ML in my home. While I don't admittedly use
> it
> > > very often, I thought the python processors were quite cool and could
> > > certainly be useful for others. My rationale is that the dependencies
> are
> > > not built into source or binary for MiNiFi C++. I would agree on the
> Java
> > > side that this would be unavoidable. While it would be preferential to
> > have
> > > the NiFi analogue I do not think it would be required when considering
> > the
> > > MiNiFi C++ processors; however, James should be the arbiter of that
> > > decision.
> > >
> > > While I disagree that the MiNiFi portion should be removed, I don't
> have
> > a
> > > strong argument to keep or remove the MiNiFI C++ code so I'd be happy
> to
> > > revert if the community feels the need to.
> > >
> > > Thanks,
> > > Marc
> > >
> > > On Mon, May 4, 2020 at 10:50 AM Joe Witt  wrote:
> > >
> > >> Team
> > >>
> > >> The below two commits raise serious concerns.
> > >>
> > >> I w

Re: MiNiFi commits for h2o

[Marc Parisi]

"We should find a way for vendors to offer extension points like this
without having to take on the burden of maintenance. How can we possibly do
this well?  We're learning this lesson the hard way in NiFi itself and this
is why the registry is being formulated."

I think there is a fine line when walking vendor tie-in. Having the
registry allows for an arm's length agreement with the Apache community. I
know others will disagree but my opinion is that extension points that
don't introduce licensing concerns from libraries should be fair game but
the fact that a paid product requires a license for that code to be useful
should not be a non-starter -- if that makes sense. I believe I stated, "I
don't have a strong argument" as I don't really have a strong opinion ( and
certainly can be wrong too ) -- so I'm interested in hearing others in
regards to this.



On Mon, May 4, 2020 at 11:38 AM Marc Parisi  wrote:

> Hi Joe,
>
> When merging I did not use the NiFi processors to test as I already have
> tooling around H20 driven ML in my home. While I don't admittedly use it
> very often, I thought the python processors were quite cool and could
> certainly be useful for others. My rationale is that the dependencies are
> not built into source or binary for MiNiFi C++. I would agree on the Java
> side that this would be unavoidable. While it would be preferential to have
> the NiFi analogue I do not think it would be required when considering the
> MiNiFi C++ processors; however, James should be the arbiter of that
> decision.
>
> While I disagree that the MiNiFi portion should be removed, I don't have a
> strong argument to keep or remove the MiNiFI C++ code so I'd be happy to
> revert if the community feels the need to.
>
> Thanks,
> Marc
>
> On Mon, May 4, 2020 at 10:50 AM Joe Witt  wrote:
>
>> Team
>>
>> The below two commits raise serious concerns.
>>
>> I want to be clear here and point out that h2o is cool.  Having such
>> integration is a neat concept and idea and one that certainly warrants
>> determination on how best to do so.
>>
>> My issue is with these two commits as it relates to licensing and
>> maintenance.
>>
>> License:
>> We should support vendors like this wanting to bring their capabilities
>> into NiFi generally sure. But the licensing and mode of use is critical.
>> In talking about this with the contributor for NiFi as well it is clear
>> that at least some or important portions of this require the user to have
>> a
>> 'driverless ai license' so they can include their jar or build pipelines
>> or
>> whatnot.  Thus it isn't usable without that first. So it might be the case
>> that this stuff is source dependent only on ASF compatible licenses in
>> terms of source - but it certainly doesn't seem to be true in terms of
>> binary dependencies. Where in the PR or JIRA is there any discussion or
>> review of the licensing?  I see plenty from James to believe this needs to
>> be reverted.  Any contrary info?
>> https://github.com/apache/nifi/pull/4242#issuecomment-622654527
>>
>>
>> Maintenance:
>> We should find a way for vendors to offer extension points like this
>> without having to take on the burden of maintenance. How can we possibly
>> do
>> this well?  We're learning this lesson the hard way in NiFi itself and
>> this
>> is why the registry is being formulated.
>>
>> JIRA/hygiene:
>> https://issues.apache.org/jira/browse/MINIFICPP-1199
>> and
>> https://issues.apache.org/jira/browse/MINIFICPP-1201
>> Both are open.  Yet we've merged commits that claim to be against each.
>>
>> I believe both of these commits need to be reverted as I do not believe
>> the
>> licensing considerations have been addressed.  I'd like to see discussion
>> on the above maintenance concern as well but that is less pressing.
>>
>>
>> Thanks
>> Joe
>>
>>
>> commit 7206c62240647520cf35649868d5d87903a256c2
>> Author: James Medel 
>> Date:   Wed Apr 29 12:38:04 2020 -0700
>>
>> MINIFI-1201: Integrate H2O Driverless AI MSP in MiNFi (#766)
>>
>> MINIFI-1201: Integrate H2O Driverless AI MSP in MiNFi (#766)
>>
>> commit 6e5f96518764df7791519c0ee625a94a207ddc69
>> Author: James Medel 
>> Date:   Wed Apr 29 12:37:00 2020 -0700
>>
>> MINIFI-1199: Integrate H2O Driverless AI PSP in MiNiFi (#763)
>>
>> * MINIFI-1199: Integrate H2O Driverless AI in MiNiFi
>>
>> MiNiFi C++ and H2O Driverless AI Integration via Custom Python
>> 

Re: MiNiFi commits for h2o

[Marc Parisi]

Hi Joe,

When merging I did not use the NiFi processors to test as I already have
tooling around H20 driven ML in my home. While I don't admittedly use it
very often, I thought the python processors were quite cool and could
certainly be useful for others. My rationale is that the dependencies are
not built into source or binary for MiNiFi C++. I would agree on the Java
side that this would be unavoidable. While it would be preferential to have
the NiFi analogue I do not think it would be required when considering the
MiNiFi C++ processors; however, James should be the arbiter of that
decision.

While I disagree that the MiNiFi portion should be removed, I don't have a
strong argument to keep or remove the MiNiFI C++ code so I'd be happy to
revert if the community feels the need to.

Thanks,
Marc

On Mon, May 4, 2020 at 10:50 AM Joe Witt  wrote:

> Team
>
> The below two commits raise serious concerns.
>
> I want to be clear here and point out that h2o is cool.  Having such
> integration is a neat concept and idea and one that certainly warrants
> determination on how best to do so.
>
> My issue is with these two commits as it relates to licensing and
> maintenance.
>
> License:
> We should support vendors like this wanting to bring their capabilities
> into NiFi generally sure. But the licensing and mode of use is critical.
> In talking about this with the contributor for NiFi as well it is clear
> that at least some or important portions of this require the user to have a
> 'driverless ai license' so they can include their jar or build pipelines or
> whatnot.  Thus it isn't usable without that first. So it might be the case
> that this stuff is source dependent only on ASF compatible licenses in
> terms of source - but it certainly doesn't seem to be true in terms of
> binary dependencies. Where in the PR or JIRA is there any discussion or
> review of the licensing?  I see plenty from James to believe this needs to
> be reverted.  Any contrary info?
> https://github.com/apache/nifi/pull/4242#issuecomment-622654527
>
>
> Maintenance:
> We should find a way for vendors to offer extension points like this
> without having to take on the burden of maintenance. How can we possibly do
> this well?  We're learning this lesson the hard way in NiFi itself and this
> is why the registry is being formulated.
>
> JIRA/hygiene:
> https://issues.apache.org/jira/browse/MINIFICPP-1199
> and
> https://issues.apache.org/jira/browse/MINIFICPP-1201
> Both are open.  Yet we've merged commits that claim to be against each.
>
> I believe both of these commits need to be reverted as I do not believe the
> licensing considerations have been addressed.  I'd like to see discussion
> on the above maintenance concern as well but that is less pressing.
>
>
> Thanks
> Joe
>
>
> commit 7206c62240647520cf35649868d5d87903a256c2
> Author: James Medel 
> Date:   Wed Apr 29 12:38:04 2020 -0700
>
> MINIFI-1201: Integrate H2O Driverless AI MSP in MiNFi (#766)
>
> MINIFI-1201: Integrate H2O Driverless AI MSP in MiNFi (#766)
>
> commit 6e5f96518764df7791519c0ee625a94a207ddc69
> Author: James Medel 
> Date:   Wed Apr 29 12:37:00 2020 -0700
>
> MINIFI-1199: Integrate H2O Driverless AI PSP in MiNiFi (#763)
>
> * MINIFI-1199: Integrate H2O Driverless AI in MiNiFi
>
> MiNiFi C++ and H2O Driverless AI Integration via Custom Python
> Processors:
> Integrates MiNiFi C++ with H2O's Driverless AI by Using Driverless AI's
> Python Scoring Pipeline and MiNiFi's Custom Python Processors. Uses the
> Python Processors to execute the Python Scoring Pipeline scorer to do batch
> scoring and real-time scoring for one or more predicted labels on test data
> in the incoming flow file content. I would like to contribute my processors
> to MiNiFi C++ as a new feature.
>
> * Update H2oPspScoreBatches processor
>
> This update includes passing "index=False" to
> "batch_scores_df.to_string(index=False)". By updating this line of code, we
> tell pandas to not include the DataFrame index when converting the
> DataFrame to a string. The reason for this update is that we don't want
> this extra column pandas tries to add to our predictions frame, we only
> want the predictions. Thus, later when the predictions get saved to a csv
> file, it will only include the predictions.
>
> * Moved ConvertDsToCsv to h2o base dir
>
> Since this ConvertDsToCsv python processor is used by the
> Python Scoring Pipeline and MOJO Scoring Pipeline processors,
> I moved ConvertDsToCsv to h2o base dir for easier access to it.
>

Re: [VOTE] Release Apache NiFi 1.11.4

[Marc Parisi]

+1 binding

* Ran through release helper guide.
* Ran build and tested in clustered mode.
*Tested site to site with minifi java without any issues or perceived
leakage.

Thanks,
Marc

On Fri, Mar 20, 2020 at 10:21 AM Andrew Lim 
wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (Catalina 10.15.2)
> -Tested secure NiFi with secure NiFi Registry 0.5.0; used NiFi Toolkit
> 1.11.4 to generate configuration/cert files
> -Ran basic flows successfully; tested basic versioned flow functionality
> -Reviewed documentation updates
>
> Drew
>
> > On Mar 18, 2020, at 1:15 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.11.4.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1159
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.4/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.4-RC1
> > The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> >
> > Checksums of nifi-1.11.4-source-release.zip:
> > SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> > SHA512:
> >
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 45 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12347022
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.4
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.11.4
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: Benchmark and Timer driven vs. Event driven

[Marc Pellmann]

Hi Mike,

thank you for your reply!

I think I need to clarify my intention. I think NiFi is a very good product
and I am
also aware of the positive aspects beside performance, that you mentioned!

It is just the difference between event vs. timer driven scheduling und the
future
plans about this. Or to rephrase this - the future proof aspect of flows,
created
with event driven scheduling.

Best regards,
Marc

On Sun, Feb 23, 2020 at 5:08 PM Mike Thomsen  wrote:

> > I just made a few benchmarks with NiFi to compare it to another solution.
>
> Raw performance is only one consideration when choosing an ETL or data
> orchestration tool. NiFi has some very critical competitive advantages such
> as how aggressively it protects the contents of the data flow from external
> failure (ex someone killing the JVM doesn't corrupt hours of work) and how
> easy it is to very deeply harden** it on the security side of things. Plus,
> you have the fact that unlike many tools in this space, it's very agile in
> being able to stop a job at any time and inspect the inputs and outputs.
>
> ** NiFi is now emerging as the de facto standard for data engineering in
> the government market in the US in part because properly hardening it is
> closer to something a well-motivated intern can do than requiring a
> "seasoned professional."
>
> On Sun, Feb 23, 2020 at 3:36 PM Marc Pellmann  wrote:
>
> > Hi,
> >
> >
> > I am interested in some insight to timer driven vs. event driven and the
> > future plans with event driven.
> >
> >
> > I just made a few benchmarks with NiFi to compare it to another solution.
> >
> >
> > The flows primarily consist of synchronous Web Service/REST like calls.
> So
> > I use HandleHttpRequest/HandleHttpResponse. In the concrete example I
> just
> > have two processors in between - a ReplaceText and a TransformXml.
> >
> >
> > From the client side I use JMeter to generate the load (just POST calls
> > with a few bytes content).
> >
> >
> > First I tested this with standard values, which means timer driven
> > scheduling strategy and 1 task.
> >
> >
> > The numbers from this tests where not very impressive, so I played with
> the
> > configuration and setted the scheduling strategy to event driven (with
> task
> > value 0 and maximum event driven thread count of 1). This could be only
> > done for the two processors between and not for the
> > HandleHttpRequest/HandleHttpResponse since they do not allow such
> > configuration.
> >
> >
> > This increased the throughput by the factor 6.
> >
> >
> > I also tested to increase the throughput with some other configurations,
> > such as more tasks or different run durations, but this did not changed
> the
> > values significantly.
> >
> >
> > So a least for this type of scenario, the event driven configuration is
> > much better. But on the other side it is still experimental and according
> > to some posts it is not seen as a good option and sounds more like it is
> > something that might be removed.
> >
> >
> > Why is this?
> >
> >
> > Also I would expect an event driven configuration option for
> > HandleHttpRequest, since there is already the event of http request
> occurs.
> >
> >
> > Best regards,
> >
> > Marc
> >
>

Re: [VOTE] Release Apache NiFi 1.11.3

[Marc Parisi]

+1 binding. Validated release and tested some of the conditions experienced
with open files ( with reporting tasks ) and did not encounter any issues.

Awesome work.

Marc

On Sun, Feb 23, 2020 at 12:10 AM Chad Zobrisky  wrote:

> +1 non-binding.
> Ran through verify release checklist and everything was as expected.
>
> Ran the PutDistributedMapCache flow uploaded to the issue and had no issues
> with open file growth after 4 hours of running.
>
> Looks good, great turn around. Thanks For RMing Joe.
>
> Chad
>
> On Sat, Feb 22, 2020 at 9:01 PM Mike Thomsen 
> wrote:
>
> > +1 binding. Set up a site to site provenance reporting task with a flow
> > that generated a high volume of junk data. Didn't see any signs of the
> > reported bug.
> >
> > On Sat, Feb 22, 2020 at 3:21 AM Joe Witt  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.11.3.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1158
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.3/
> > >
> > > A helpful reminder on how the release candidate verification process
> > works:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >
> > > The Git tag is nifi-1.11.3-RC1
> > > The Git commit ID is 10b509cf5bb88b12b0dd497543291f3c49a9903f
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=10b509cf5bb88b12b0dd497543291f3c49a9903f
> > >
> > > Checksums of nifi-1.11.3-source-release.zip:
> > > SHA256:
> b2544719a8de02892b3436f1e6084b9b6011bf706a183fa2f059a9961634a7bd
> > > SHA512:
> > >
> > >
> >
> 353671e06dd60e186d2a9a29eb9b7c2d183757f6a0f76801b4ecb5d87aab99e701b9ebde932ee414d4b304afd2bd1d0a0e574906a385cfafc8de36cc47c2d0a3
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 14 issues were closed/resolved for this release:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12347022
> > >
> > > Release note highlights can be found here:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.3
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build
> > > from source, and test. Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.11.3
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>

Benchmark and Timer driven vs. Event driven

[Marc Pellmann]

Hi,


I am interested in some insight to timer driven vs. event driven and the
future plans with event driven.


I just made a few benchmarks with NiFi to compare it to another solution.


The flows primarily consist of synchronous Web Service/REST like calls. So
I use HandleHttpRequest/HandleHttpResponse. In the concrete example I just
have two processors in between - a ReplaceText and a TransformXml.


>From the client side I use JMeter to generate the load (just POST calls
with a few bytes content).


First I tested this with standard values, which means timer driven
scheduling strategy and 1 task.


The numbers from this tests where not very impressive, so I played with the
configuration and setted the scheduling strategy to event driven (with task
value 0 and maximum event driven thread count of 1). This could be only
done for the two processors between and not for the
HandleHttpRequest/HandleHttpResponse since they do not allow such
configuration.


This increased the throughput by the factor 6.


I also tested to increase the throughput with some other configurations,
such as more tasks or different run durations, but this did not changed the
values significantly.


So a least for this type of scenario, the event driven configuration is
much better. But on the other side it is still experimental and according
to some posts it is not seen as a good option and sounds more like it is
something that might be removed.


Why is this?


Also I would expect an event driven configuration option for
HandleHttpRequest, since there is already the event of http request occurs.


Best regards,

Marc

Re: [VOTE] Release Apache NiFi 1.11.2 (rc1)

[Marc Parisi]

 ran this over the weekend but forgot to respond.

 I saw the other chain, which reminded me to respond. Sorry about that...

Ran my typical release build following the helper guide. Used my typical
test flow.

+1 if we can extend the vote, otherwise I'll jump on RC2.

On Fri, Feb 14, 2020 at 10:15 PM Joe Witt  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.11.2.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1157
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.2/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.11.2-RC1
> The Git commit ID is 6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
>
> Checksums of nifi-1.11.2-source-release.zip:
> SHA256: 2a030956a7cc9578e616195dd4cf8a853976e17eb040a7b216f844ae2ce9a610
> SHA512:
>
> 135101f3f9b37b559e850e79c89bad36d707126fcea559fa4f6846c4cb21c17ab51c119c5005df359a4d3a066c66611b00816c2f7586b24d34f0f418d4b5c527
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 14 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346972
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.2
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.11.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: Documentation Issues

[Marc Parisi]

Hi Jim,
  Thank you for reaching out. Would you be willing to submit a pull request
with some clarification and justification regarding documentation changes?
The docs in question are here :
https://github.com/apache/nifi/tree/master/nifi-docs

 The community is always welcoming of ideas and improvements from others.
  Best,
  Marc


On Thu, Feb 13, 2020, 6:18 PM Jim Laskowski 
wrote:

> Regarding https://nifi.apache.org/docs/nifi-docs/html/overview.html, “The
> core concepts of Nifi,” I think the term “process” and  “processor” should
> not be used interchangeably.  Nowhere else in the computer science field
> have I seen these two words used interchangeably, and rightly so because
> they have different definitions in English.
>
>
>
>
>
>
>
>
>
>
>
>
> If your messaging client supports TLS for secure connections, then this
> message was sent securely via TLS from Medecision, Inc. This e-mail
> communication, including any attached files may contain material that is
> proprietary, privileged, confidential, or otherwise legally exempt from
> disclosure. This communication is intended solely for the use of the
> individual or entity to which it is addressed. If you are not the intended
> recipient or the person responsible for delivering this communication to
> the intended recipient, you are prohibited from retaining, using,
> disseminating, forwarding, printing or copying this communication. If you
> have received this communication in error, please immediately notify the
> sender via return e-mail or telephone. This email has been scanned and
> found to be virus free. If this message contains a virus, please contact
> disclai...@medecision.com.
>

Re: [VOTE] Release Apache NiFi 1.11.1 (rc1)

[Marc Parisi]

+1 binding

 Verified sigs, hashes, etc per the typical release helper process.

  Since the list of resolved issues were so small I verified most, with the
exception of 7051, 7080, and 7069. All others appear to be resolved.
  Only built on PopOS and Centos due to superbowl -- but everything looks
good.


On Mon, Feb 3, 2020 at 4:04 AM Yoshiaki Takahashi 
wrote:

> +1 (non-binding)
>
> - [x] Non-RPM (usual) build with Java 8.
> - [x] Deploy on 3 node secured cluster in CentOS 7.7.0 and run on Java 8.
> - [x] Non-RPM (usual) build with Java 11.
> - [x] Deploy on 1 node non secured cluster in CentOS 7.7.0 and run on Java
> 11.
>
> Thanks for working for the release!
>
> On 2020/01/31 20:11:00, Joe Witt  wrote:
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.11.1.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1156
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.1/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.1-RC1
> > The Git commit ID is d22858d045fb3e5343a87d362855810963aa8556
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=d22858d045fb3e5343a87d362855810963aa8556
> >
> > Checksums of nifi-1.11.1-source-release.zip:
> > SHA256: 41878981689e08c51ed7bb921c46f6328c1e6b6c94460a2382069bd042ab7112
> > SHA512:
> >
> d309342732196225ffdbac3eaeed3c9b949bcee00509fb6d073618d869c6db56b426f5867849a8ae752d7acc8c6dd18a14cb377655774d86f91d736350eb2041
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 9 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346906
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.1
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.11.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [VOTE] Release Apache NiFi 1.11.0 (rc3)

[Marc Parisi]

+1 (binding)

Ran through helper guide for validation.

Built on pop os and osx.

Ran a high throughout test flow, where I encountered no regressions across
several record oriented processors and non secure site to site.

Thanks,
Marc


On Tue, Jan 21, 2020, 4:43 PM Andrew Lim  wrote:

> +1 (non-binding)
>
> -Ran full clean install on OS X (Catalina 10.15.2)
> -Tested secure NiFi with secure NiFi Registry
> -Ran basic flows successfully
> -Reviewed core UI and documentation fixes/updates
>
> In setting up my secure NiFi and secure NiFi registry, I used the NiFi TLS
> Toolkit [1] to create my config files and certs. I was able to access the
> UIs of both apps using Safari but not able to with Chrome due to a
> NET::ERR_CERT_REVOKED error which I had never seen before.  Turns out this
> is a known issue on Catalina [2]. MacOSX 10.15 requires certs to be valid
> for 825 days or less and a minimum 2048 bit key.  By default, the TLS
> Toolkit sets the validity to 1095 days and the number of bits for generated
> keys to 2048. Creating new certs with the required 825 validity solved the
> issue. I will add a note to the Toolkit Guide for this new requirement [3].
>
> Drew
>
> [1]
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> <
> https://nifi.apache.org/docs/nifi-docs/html/toolkit-guide.html#tls_toolkit
> >
> [2] https://support.apple.com/en-us/HT210176 <
> https://support.apple.com/en-us/HT210176>
> [3] https://issues.apache.org/jira/browse/NIFI-7053 <
> https://issues.apache.org/jira/browse/NIFI-7053>
>
>
> > On Jan 19, 2020, at 3:21 PM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > nifi-1.11.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1155
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.0-RC3
> > The Git commit ID is 633408bce7ad34dad727ed9c4edfd36a224f3f12
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=633408bce7ad34dad727ed9c4edfd36a224f3f12
> >
> > Checksums of nifi-1.11.0-source-release.zip:
> > SHA256: 0e2d77265fc7cedfbdb9588df1dd7f456fd18b6288d65eb5e21befe23af7c567
> > SHA512:
> >
> 4880fa3482b3e8d8eed439848fe0a6596826d7ad46425a91b0dd4a4bcd178259327380b24045b7991dbdf8449abdfdda145786b6863eb603f6cef3b9e0ae8ec1
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 129 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346451
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.11.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: Release vote on Catalina?

[Marc Parisi]

Mike my osx builds are also Catalina based. I usually add -T2C but don't
recall if I added that to the release vote build. The output was
successful, though.

 If it only sporadically occurs I can retry a few more times or run in a
loop tomorrow.

On Fri, Jan 17, 2020, 7:10 PM Joe Witt  wrote:

> Command I use to build:
>
> mvn -T 1C clean install -Pinclude-grpc -Ddir-only
>
>
>
> JAVA 8 on Catalina
>
> ……
>
> [INFO] nifi-system-test-extensions-nar  SUCCESS [
> 0.832
> s]
>
> [INFO] nifi-system-test-extensions2-bundle  SUCCESS [
> 0.044
> s]
>
> [INFO] nifi-system-test-extensions2 ... SUCCESS [
> 2.675
> s]
>
> [INFO] nifi-system-test-extensions2-nar ... SUCCESS [
> 0.461
> s]
>
> [INFO] nifi-system-test-suite . SUCCESS [
> 2.630
> s]
>
> [INFO]
> 
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> 
>
> [INFO] Total time:  12:21 min (Wall Clock)
>
> [INFO] Finished at: 2020-01-17T18:58:31-05:00
>
> [INFO]
> 
>
> $ mvn -version
>
> Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
> 2019-08-27T11:06:16-04:00)
>
> Maven home: /usr/local/Cellar/maven/3.6.2/libexec
>
> Java version: 1.8.0_202, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_202.jdk/Contents/Home/jre
>
> Default locale: en_US, platform encoding: UTF-8
>
> OS name: "mac os x", version: "10.15.2", arch: "x86_64", family: "mac"
>
> $ uname -a
>
> Darwin macbook.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov  9
> 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
>
>
>
>
> Java 11 on Catalina
>
> …….
>
> [INFO] nifi-system-test-extensions-nar  SUCCESS [
> 1.393
> s]
>
> [INFO] nifi-system-test-extensions2-bundle  SUCCESS [
> 0.185
> s]
>
> [INFO] nifi-system-test-extensions2 ... SUCCESS [
> 3.947
> s]
>
> [INFO] nifi-system-test-extensions2-nar ... SUCCESS [
> 1.373
> s]
>
> [INFO] nifi-system-test-suite . SUCCESS [
> 3.257
> s]
>
> [INFO]
> 
>
> [INFO] BUILD SUCCESS
>
> [INFO]
> 
>
> [INFO] Total time:  13:48 min (Wall Clock)
>
> [INFO] Finished at: 2020-01-17T18:37:39-05:00
>
> [INFO]
> 
>
> $ mvn -version
>
> Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
> 2019-08-27T11:06:16-04:00)
>
> Maven home: /usr/local/Cellar/maven/3.6.2/libexec
>
> Java version: 11.0.4, vendor: AdoptOpenJDK, runtime:
> /Library/Java/JavaVirtualMachines/adoptopenjdk-11.jdk/Contents/Home
>
> Default locale: en_US, platform encoding: UTF-8
>
> OS name: "mac os x", version: "10.15.2", arch: "x86_64", family: "mac"
>
> $ uname -a
>
> Darwin macbook.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov  9
> 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
>
> On Fri, Jan 17, 2020 at 6:20 PM Joe Witt  wrote:
>
> > ill build on catalina now and let you know what i see
> >
> > thanks
> >
> > On Fri, Jan 17, 2020 at 6:15 PM Mike Thomsen 
> > wrote:
> >
> >> That makes me strongly suspect that the problems I've had with a few
> unit
> >> tests are an OS issue.
> >>
> >> On Fri, Jan 17, 2020 at 2:26 PM Joe Witt  wrote:
> >>
> >> > I did it on macOS Mojave and Fedora 31.
> >> >
> >> > Thanks
> >> >
> >> > On Fri, Jan 17, 2020 at 2:18 PM Mike Thomsen 
> >> > wrote:
> >> >
> >> > > My company recently updated my MBP to Catalina. Is anyone else doing
> >> the
> >> > > release vote on that version of macOS?
> >> > >
> >> > > Thanks,
> >> > >
> >> > > Mike
> >> > >
> >> >
> >>
> >
>

Re: [VOTE] Release Apache NiFi 1.11.0 (rc2)

[Marc Parisi]

+1 Binding to release

   Followed the release helper guide -- didn't see any license issues, all
looks good.
   I built and ran with some custom NARs on a sizable Apache NiFi Cluster
running a high throughput workload that I used to validate 1.10 -- no
issues encountered or performance degradation.


  Thanks for pulling this RC together, Joe.


On Fri, Jan 17, 2020 at 11:38 AM Marton Szasz  wrote:

> +1
> Hashes and signature are fine.
> Build and tests work after setting JAVA_HOME.
> NiFi works with a simple flow.
>
> On Fri, 17 Jan 2020 at 16:55, Arpad Boda 
> wrote:
> >
> > +1
> >
> > Verified signature and hashes
> > Built and tests passed
> > NiFi started, created a simple flow
> > Transferred flowfiles using raw S2S
> >
> > All worked perfectly
> >
> > On Fri, Jan 17, 2020 at 2:58 PM Shawn Weeks 
> > wrote:
> >
> > > +1 Build runs fine and hashes match.
> > >
> > > On 1/16/20, 4:54 PM, "Joe Witt"  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of
> Apache
> > > NiFi
> > > nifi-1.11.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found
> at:
> > >
> https://repository.apache.org/content/repositories/orgapachenifi-1153
> > >
> > > The source being voted upon and the convenience binaries can be
> found
> > > at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
> > >
> > > The Git tag is nifi-1.11.0-RC2
> > > The Git commit ID is 97bec7ad0f1efe3e28ac9cb7d2364134727cd07b
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=97bec7ad0f1efe3e28ac9cb7d2364134727cd07b
> > >
> > > Checksums of nifi-1.11.0-source-release.zip:
> > > SHA256:
> > > f43245e21dba63061a7f5bc8e2590f1242112380083791acff10a07ecf357234
> > > SHA512:
> > >
> > >
> 4634981608af35b76a96375e84660fbb75148e67ab1d0b6c192ee01eeb7c9a4cb1ebd7671ad73fa27a8e9bb71f361e32f49214573be5564d781612316cc8f88f
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 112 issues were closed/resolved for this release:
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346451
> > >
> > > Release note highlights can be found here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary
> items
> > > including checking hashes, signatures, build
> > > from source, and test. Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.11.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > >
>

Re: [VOTE] Release Apache NiFi 1.10.0 (rc3)

[Marc Parisi]

+1
   Verified sigs/hashes, built and ran example flows on my server
machine(s) running the same flow across different operating systems. Used
Apache NIFi MiNiFi as an ingress to NiFi for common test flow that I use.

   Awesome work getting this out!

On Thu, Oct 31, 2019 at 9:56 PM Robert Fellows 
wrote:

> +1 (non-binding)
>
> [X] Verified the checksums
> [X] Verified signature
> [X] Verify build (java 11)
> [X] Verify general functionality (including parameter contexts and
> back-pressure prediction UI)
>
> On Thu, Oct 31, 2019 at 10:00 AM Peter Turcsanyi 
> wrote:
>
> > +1 (non-binding)
> >
> > Verified checksums and signatures.
> > Built source with empty Maven repo (tests ok, contrib-check ok).
> > Tested some flows (all AWS processors, focusing on the new S3 features:
> > encryption, storage classes, requester pays).
> >
> > Peter
> >
> > On Thu, Oct 31, 2019 at 2:28 PM Bryan Bende  wrote:
> >
> > > +1 (binding)
> > >
> > > Everything in release helper checked out. I did run into a test
> > > failure the first time building the source, but then trying again
> > > succeeded. I think it is a sporadic failure we have seen before...
> > >
> > > [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time
> > > elapsed: 1.415 s <<< FAILURE! - in
> > > org.apache.nifi.wali.TestLengthDelimitedJournal
> > > [ERROR]
> > >
> >
> testFailureDuringWriteCannotCauseCorruption(org.apache.nifi.wali.TestLengthDelimitedJournal)
> > >  Time elapsed: 1.022 s  <<< FAILURE!
> > > java.lang.AssertionError: expected:<0> but was:<2>
> > > at
> > >
> >
> org.apache.nifi.wali.TestLengthDelimitedJournal.testFailureDuringWriteCannotCauseCorruption(TestLengthDelimitedJournal.java:585)
> > >
> > > On Thu, Oct 31, 2019 at 6:42 AM Kotaro Terada 
> > wrote:
> > > >
> > > > Thanks for taking care of it, Pierre and Joe!
> > > >
> > > > > Please note only PMC votes are binding.
> > > >
> > > > I got it,  I'll be careful next time.
> > > >
> > > > Thanks,
> > > > Kotaro
> > > >
> > > >
> > > > On Thu, Oct 31, 2019 at 7:32 PM Joe Witt  wrote:
> > > >
> > > > > Id just flag this on release notes and we can fix for the next
> > release.
> > > > >
> > > > > Kotaro good find.  Please note only PMC votes are binding.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Thu, Oct 31, 2019 at 6:27 AM Pierre Villard <
> > > > > pierre.villard...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Good catch Kotaro! I merged the fix for #2. The fix for #1 LGTM
> but
> > > I'll
> > > > > > let the guys who worked on the Java 11 bits look into it.
> > > > > >
> > > > > > Joe, I didn't set the fix version on the JIRA and will wait until
> > we
> > > > > reach
> > > > > > a decision regarding this RC.
> > > > > >
> > > > > > Le jeu. 31 oct. 2019 à 11:08, Kotaro Terada 
> a
> > > > > écrit :
> > > > > >
> > > > > > > -1 (binding), due to the following problems I found.
> > > > > > >
> > > > > > > (1) NiFi doesn't start up from the rpm build on Java 11.
> > > > > > >
> > > > > > > We have a mismatch in the "lib" directories of rpm and non-rpm
> > > build.
> > > > > > This
> > > > > > > causes that NiFi (with Java 11) doesn't start up from the rpm
> > > build.
> > > > > Some
> > > > > > > jar files should be located in the "lib/bootstrap/" but they
> are
> > > > > > currently
> > > > > > > in "lib/".
> > > > > > >
> > > > > > > I checked the following behaviors:
> > > > > > > - Non-RPM (usual) build with Java 8 and run on Java 8... OK
> > > > > > > - Non-RPM (usual) build with Java 11 and run on Java 11... OK
> > > > > > > - RPM build with Java 8 and run on Java 8... OK (isn't affected
> > by
> > > the
> > > > > > lib
> > > > > > > mismatch)
> > > > > > > - RPM build with Java 11 and run on Java 11... NiFi doesn't
> start
> > > (this
> > > > > > > problem)
> > > > > > >
> > > > > > > I created a JIRA and a PR to fix it:
> > > > > > > https://issues.apache.org/jira/browse/NIFI-6827
> > > > > > >
> > > > > > > (2) There is an unintentional string in "conf/logback.xml".
> > > > > > >
> > > > > > > The "conf/logback.xml" seems to have an unintentional string
> > > > > > > "MockProcessContext". I guess this was slipped into it by the
> > > merging
> > > > > > > commit of https://github.com/apache/nifi/pull/3773
> > > unintentionally.
> > > > > > >
> > > > > > > I created a JIRA and a PR to fix it:
> > > > > > > https://issues.apache.org/jira/browse/NIFI-6828
> > > > > > >
> > > > > > > Could you take a look at them, please?
> > > > > > >
> > > > > > > Thanks for working for the release!
> > > > > > > Kotaro
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Oct 31, 2019 at 6:10 PM Pierre Villard <
> > > > > > > pierre.villard...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1 (binding)
> > > > > > > >
> > > > > > > > Went through the release helper guide and it LGTM. Deployed
> > > > > > > > secured/unsecured standalone/cluster instances on Google
> Cloud
> > > with
> > > > > > > various
> > > > > > > > flows including the new BigQuery proce

Re: [ANNOUNCE] New Apache NiFi Committer Dániel Bakai

[Marc Parisi]

Congrats!

On Fri, Oct 25, 2019, 11:51 PM Sivaprasanna 
wrote:

> Congratulations, Daniel. All the very best.
>
> On Sat, 26 Oct 2019 at 6:01 AM, Tony Kurc  wrote:
>
> > Congratulations Dániel!
> >
> > On Fri, Oct 25, 2019, 8:21 PM Otto Fowler 
> wrote:
> >
> > > std::cout << “Congratulations” << std::endl;
> > >
> > >
> > >
> > >
> > > On October 25, 2019 at 12:38:20, Aldrin Piri (ald...@apache.org)
> wrote:
> > >
> > > Apache NiFi community,
> > >
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> > Dániel
> > > has accepted the PMC's invitation to become a committer on the Apache
> > NiFi
> > > project. We greatly appreciate all of Dániel's hard work and generous
> > > contributions to the project. We look forward to continued involvement
> > > in the project.
> > >
> > > Dániel has provided numerous contributions to the MiNiFi C++ codebase,
> > > discovering and providing fixes for bugs, new functionality, and
> > improving
> > > build processes. Dániel is also a staple in review processes and
> > > approaches each interaction with great communication and
> professionalism.
> > >
> > > Welcome and congratulations!
> > > AP
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Rob Fellows

[Marc Parisi]

Congrats Rob!

On Wed, Sep 25, 2019 at 9:59 AM Rob Moran  wrote:

> Thanks for all your work, Rob -- congrats!
>
> On Wed, Sep 25, 2019 at 9:29 AM Andrew Lim 
> wrote:
>
> > Congrats Rob!
> >
> >
> > > On Sep 24, 2019, at 7:56 PM, Tony Kurc  wrote:
> > >
> > > Apache NiFi community,
> > > On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Rob
> > > has accepted the PMC's invitation to become a committer on the Apache
> > NiFi
> > > project. We greatly appreciate all of Rob's hard work and generous
> > > contributions to the project. We look forward to his continued
> > involvement
> > > in the project.
> > >
> > > What stood out with Rob are his regular code contributions and reviews
> on
> > > many parts of the project to include NiFi, NiFi FDS, and NiFi Registry
> > > since early this year. Additionally, he's been doing the
> > > not-always-glamorous work of helping verify releases, which was a huge
> > > assist in getting NiFi 1.9.1, NiFi Registry 0.4.0 and 0.5.0, and NiFi
> FDS
> > > 0.2.0 out to the community.
> > >
> > > Welcome and congratulations!
> > > Tony
> >
> >
>

Re: MiNiFi Python Dependencies (Anaconda)

[Marc Parisi]

Hi Jeremy,
  The env variable I sent can be set or appended prior to running minifi,
without the need to recompile.

On Thu, Aug 29, 2019, 3:38 PM Jeremy Dyer  wrote:

> So are you saying I need to build and link against my conda python binary?
>
> On Thu, Aug 29, 2019 at 6:47 AM Marc Parisi  wrote:
>
> > Hi Jeremy,
> >
> >   Apache NiFi MiNiFi C++ python processors support virtual environments;
> > however, I don't think the library links, once the binary is built, will
> be
> > overridden through conda's environment activation ( only PATH is updated
> if
> > I recall correctly )
> >
> >   I could be off base on the problem you are experiencing -- but one way
> > I've solved this with my Anacaonda environment has been to use
> > LD_LIBRARY_PATH. When I use the following command: export
> > LD_LIBRARY_PATH=/home/0x/anaconda3/lib/
> >
> >   After this I no longer link to the system provided version of python
> > libraries but instead to
> > /home/0x/anaconda3/lib/libpython3.7m.so.1.0 .
> >
> >   This is actually something I've seen detected via scripts so it is
> > possible for minifi.sh to (potentially) handle this.
> >
> >   Let me know if this solves the issue.
> >
> >   Best Regards,
> >   Marc
> >
> > On Wed, Aug 28, 2019 at 8:29 PM Jeremy Dyer 
> wrote:
> >
> > > Hello all,
> > >
> > > I'm trying to use the MiNiFi C++ Python processors feature. I have used
> > > this with great results in the past but I'm trying to load some
> libraries
> > > that are installed in my Python conda virtual environment.
> > >
> > > I have activated my environment and then run the ./bin/minifi binary
> > under
> > > the same user but the process doesn't seem to pickup my Python library
> > that
> > > I am trying to import. Does anyone have any thought on how I can make
> my
> > > virtual environment path visible to the MiNiFi agent binary so those
> > > libraries can be used in MiNiFi?
> > >
> > > Thanks,
> > > Jeremy Dyer
> > >
> >
>

Re: MiNiFi Python Dependencies (Anaconda)

[Marc Parisi]

Hi Jeremy,

  Apache NiFi MiNiFi C++ python processors support virtual environments;
however, I don't think the library links, once the binary is built, will be
overridden through conda's environment activation ( only PATH is updated if
I recall correctly )

  I could be off base on the problem you are experiencing -- but one way
I've solved this with my Anacaonda environment has been to use
LD_LIBRARY_PATH. When I use the following command: export
LD_LIBRARY_PATH=/home/0x/anaconda3/lib/

  After this I no longer link to the system provided version of python
libraries but instead to
/home/0x/anaconda3/lib/libpython3.7m.so.1.0 .

  This is actually something I've seen detected via scripts so it is
possible for minifi.sh to (potentially) handle this.

  Let me know if this solves the issue.

  Best Regards,
  Marc

On Wed, Aug 28, 2019 at 8:29 PM Jeremy Dyer  wrote:

> Hello all,
>
> I'm trying to use the MiNiFi C++ Python processors feature. I have used
> this with great results in the past but I'm trying to load some libraries
> that are installed in my Python conda virtual environment.
>
> I have activated my environment and then run the ./bin/minifi binary under
> the same user but the process doesn't seem to pickup my Python library that
> I am trying to import. Does anyone have any thought on how I can make my
> virtual environment path visible to the MiNiFi agent binary so those
> libraries can be used in MiNiFi?
>
> Thanks,
> Jeremy Dyer
>

Re: [VOTE] Release Apache NiFi Registry 0.5.0

[Marc Parisi]

+1 ( binding )

  Performed checks as described in the helper guide, performing my usual
testing. Looks great!

On Fri, Aug 23, 2019 at 3:54 PM Matt Gilman  wrote:

> +1 (binding)
>
> Ran through helper. Verified recent improvements to ignore case when
> defining groups from a directory server. Tested other basic operations.
> Looked great.
>
> Thanks for RMing Bryan!!
>
> On Wed, Aug 21, 2019 at 2:31 PM Bryan Bende  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry nifi-registry-0.5.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1147
> >
> > The Git tag is nifi-registry-0.5.0-RC1
> > The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
> >
> > Checksums of nifi-registry-0.5.0-source-release.zip:
> > SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b
> > SHA512:
> >
> 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 28 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12345561
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > Then please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.5.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: Problems with build in non-english (german) environment

[Marc Pellmann]

Hi Jeff,

yes, my issue is fixed with your PR!

Thanks,
Marc

On Wed, Aug 7, 2019 at 9:05 PM Jeff  wrote:

> Marc,
>
> Your issue will most likely be resolved by NIFI-6529 [1], for which I
> submitted PR 3639 [2].  If you get a chance, please check out PR 3639 and
> run the tests as described in the PR.  You can update user.language and
> user.region in the mvn command line to use your particular locale.
>
> [1] https://issues.apache.org/jira/browse/NIFI-6529
> [2] https://github.com/apache/nifi/pull/3639
>
> On Wed, Aug 7, 2019 at 10:40 AM Arpad Boda  wrote:
>
> > I think there are more of these:
> > https://issues.apache.org/jira/browse/NIFI-5750
> >
> > On Wed, Aug 7, 2019 at 7:54 AM Marc Pellmann  wrote:
> >
> > > Hi Pierre,
> > >
> > > thank you for your reply! It should be reproduce-able with setting the
> > > german locale in the pom:
> > >
> > > -Duser.language=de -Duser.country=DE
> > > -Duser.region=DE
> > >
> > > Thanks,
> > > Marc
> > >
> > > On Wed, Aug 7, 2019 at 1:21 PM Pierre Villard <
> > pierre.villard...@gmail.com
> > > >
> > > wrote:
> > >
> > > > I filed a JIRA NIFI-6531 [1], and will look into it.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-6531
> > > >
> > > > Le mer. 7 août 2019 à 11:37, Pierre Villard <
> > pierre.villard...@gmail.com
> > > >
> > > > a
> > > > écrit :
> > > >
> > > > > Hi Marc,
> > > > >
> > > > > This should not happen as we are trying to have a build locale
> > > agnostic.
> > > > > If you can list the failing tests and/or file a JIRA, that would be
> > > > > awesome. I'll definitely have a look on my side.
> > > > >
> > > > > The workaround you suggested about modifying the pom for the
> surefire
> > > > > plugin is the best way to go AFAIK.
> > > > >
> > > > > Thanks,
> > > > > Pierre
> > > > >
> > > > >
> > > > > Le mer. 7 août 2019 à 11:05, Marc Pellmann  a
> > > écrit
> > > > :
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> I tried to build NiFi from source and had some problems with my
> > german
> > > > >> OS(X). Some tests did not passed because there have been errors
> > with .
> > > > vs
> > > > >> ,
> > > > >> in the tests.
> > > > >>
> > > > >> Example:
> > > > >>
> > > > >> [ERROR]
> > testFormatDataSize(org.apache.nifi.processor.TestFormatUtils)
> > > > >> Time
> > > > >> elapsed: 0.004 s <<< FAILURE! org.junit.ComparisonFailure:
> > > > >> expected:<10[.]4
> > > > >> bytes> but was:<10[,]4 bytes> at
> > > > >>
> > > > >>
> > > >
> > >
> >
> org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
> > > > >>
> > > > >> Of course it works when I switch my OS to english/US, but that is
> > not
> > > > >> really a solution. To set this with system variables like
> > > > >> JAVA_TOOL_OPTIONS
> > > > >> with -Duser.language=en -Duser.country=US -Duser.region=US did not
> > > > worked.
> > > > >>
> > > > >> The only solution was to set it in the pom.xml for the surefire
> > plugin
> > > > >> directly:
> > > > >>
> > > > >> -Duser.language=en -Duser.country=US
> > > > >> -Duser.region=US
> > > > >>
> > > > >> Is there a different solution? Or if not - shouldn't this be the
> > > > default?
> > > > >>
> > > > >> Thanks,
> > > > >>
> > > > >> Marc
> > > > >>
> > > > >
> > > >
> > >
> >
>

Re: Problems with build in non-english (german) environment

[Marc Pellmann]

Hi Pierre,

thank you for your reply! It should be reproduce-able with setting the
german locale in the pom:

-Duser.language=de -Duser.country=DE
-Duser.region=DE

Thanks,
Marc

On Wed, Aug 7, 2019 at 1:21 PM Pierre Villard 
wrote:

> I filed a JIRA NIFI-6531 [1], and will look into it.
>
> [1] https://issues.apache.org/jira/browse/NIFI-6531
>
> Le mer. 7 août 2019 à 11:37, Pierre Villard 
> a
> écrit :
>
> > Hi Marc,
> >
> > This should not happen as we are trying to have a build locale agnostic.
> > If you can list the failing tests and/or file a JIRA, that would be
> > awesome. I'll definitely have a look on my side.
> >
> > The workaround you suggested about modifying the pom for the surefire
> > plugin is the best way to go AFAIK.
> >
> > Thanks,
> > Pierre
> >
> >
> > Le mer. 7 août 2019 à 11:05, Marc Pellmann  a écrit
> :
> >
> >> Hi,
> >>
> >> I tried to build NiFi from source and had some problems with my german
> >> OS(X). Some tests did not passed because there have been errors with .
> vs
> >> ,
> >> in the tests.
> >>
> >> Example:
> >>
> >> [ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils)
> >> Time
> >> elapsed: 0.004 s <<< FAILURE! org.junit.ComparisonFailure:
> >> expected:<10[.]4
> >> bytes> but was:<10[,]4 bytes> at
> >>
> >>
> org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)
> >>
> >> Of course it works when I switch my OS to english/US, but that is not
> >> really a solution. To set this with system variables like
> >> JAVA_TOOL_OPTIONS
> >> with -Duser.language=en -Duser.country=US -Duser.region=US did not
> worked.
> >>
> >> The only solution was to set it in the pom.xml for the surefire plugin
> >> directly:
> >>
> >> -Duser.language=en -Duser.country=US
> >> -Duser.region=US
> >>
> >> Is there a different solution? Or if not - shouldn't this be the
> default?
> >>
> >> Thanks,
> >>
> >> Marc
> >>
> >
>

Problems with build in non-english (german) environment

[Marc Pellmann]

Hi,

I tried to build NiFi from source and had some problems with my german
OS(X). Some tests did not passed because there have been errors with . vs ,
in the tests.

Example:

[ERROR] testFormatDataSize(org.apache.nifi.processor.TestFormatUtils)  Time
elapsed: 0.004 s <<< FAILURE! org.junit.ComparisonFailure: expected:<10[.]4
bytes> but was:<10[,]4 bytes> at
org.apache.nifi.processor.TestFormatUtils.testFormatDataSize(TestFormatUtils.java:91)

Of course it works when I switch my OS to english/US, but that is not
really a solution. To set this with system variables like JAVA_TOOL_OPTIONS
with -Duser.language=en -Duser.country=US -Duser.region=US did not worked.

The only solution was to set it in the pom.xml for the surefire plugin
directly:

-Duser.language=en -Duser.country=US
-Duser.region=US

Is there a different solution? Or if not - shouldn't this be the default?

Thanks,

Marc

Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)

[Marc Parisi]

+1 (binding). I built and tested according to the release helper guide.
Demo app, hashes, readmes, and notices all look good.

Thanks Scott!

On Fri, Jul 26, 2019 at 10:09 AM Matt Gilman 
wrote:

> +1 (binding) Release this package as nifi-fds-0.2.0
>
> Ran through release helper. Checked out demo app and all looks good.
>
> Thanks for RMing Scott!
>
> Matt
>
> On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras  >
> wrote:
>
> > * Verified the signature
> > * Verified the hashes
> > * Verified README
> > * Verified the demo app works as expected
> >
> > Unfortunately majority of npm scripts are broken on windows, however I
> > could make them run and test the app with some minor changes. JIRA issue:
> > https://issues.apache.org/jira/browse/NIFI-6481
> >
> > + 1 (non-binding)
> >
> > András
> >
> > On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis
>  > >
> > wrote:
> >
> > > * Verified the git commit
> > > * Verified the signature
> > > * Verified the hashes
> > > * Verified the build
> > > * Verified README
> > > * Verified the demo app works as expected
> > >
> > > + 1 (non-binding)
> > >
> > > Cheers,
> > > Adam
> > >
> > > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows 
> > > wrote:
> > >
> > > > * Verified the signature
> > > > * Verified the hashes
> > > > * Verified the build
> > > > * Verified README
> > > > * Verified the demo app works as expected
> > > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked
> with
> > > > documented updates.
> > > >
> > > > + 1 (non-binding)
> > > >
> > > >
> > > > -- Rob Fellows
> > > >
> > > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan 
> > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > >
> > > > > I am pleased to be calling this vote for the source release of
> Apache
> > > > >
> > > > > NiFi Flow Design System 0.2.0.
> > > > >
> > > > >
> > > > > The source zip, including signatures, etc. can be found at:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
> > > > >
> > > > >
> > > > > The Git tag is NIFI-FDS-0.2.0-RC2
> > > > >
> > > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17
> > > > >
> > > > >
> > > > > Checksums of nifi-fds-0.2.0-source-release.zip:
> > > > >
> > > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d
> > > > >
> > > > > SHA256:
> > > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f
> > > > >
> > > > > SHA512:
> > > > >
> > > > >
> > > >
> > >
> >
> 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1
> > > > >
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > >
> > > > > https://people.apache.org/keys/committer/scottyaslan.asc
> > > > >
> > > > >
> > > > > KEYS file available here:
> > > > >
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > >
> > > > > 36 issues were closed/resolved for this release:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453&projectId=12316020
> > > > >
> > > > >
> > > > > Release note highlights can be found here:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0
> > > > >
> > > > >
> > > > > The vote will be open for 72 hours.
> > > > >
> > > > >
> > > > > Please download the release candidate and evaluate the necessary
> > items
> > > > >
> > > > > including checking hashes, signatures, build from source, and test.
> > > > >
> > > > >
> > > > > The please vote:
> > > > >
> > > > >
> > > > > [ ] +1 Release this package as nifi-fds-0.2.0
> > > > >
> > > > > [ ] +0 no opinion
> > > > >
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > >
> > > >
> > > > --
> > > > ---
> > > > Rob Fellows
> > > >
> > >
> >
>

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.6.1

[Marc Parisi]

Good find! I'm +1 on adding that fix piggy backed on the aforementioned
test ticket. There are almost no tests on listen http and it has been a
risk for some time.

I'd like to avoid adding any fixes without those tests in 814 ( we'll end
up fixing in master and cherry picking). Happy to help as time allows but I
think this bug has been around long enough that we can suffer the time to
add those tests if we want it fixed in 0.6.1

On Tue, Jul 9, 2019, 12:24 PM Daniel Bakai  wrote:

> Hi,
>
> I am working on https://issues.apache.org/jira/browse/MINIFICPP-814,
> and unfortunately https support in ListenHTTP seems to be broken since
> https://github.com/apache/nifi-minifi-cpp/pull/394 was merged, which
> disabled SSL support in civetweb.
> This unfortunately means that it is broken in 0.6.0 as well as on master.
> I have verified this with the macOS binary release of 0.6.0.
> I propose we discuss whether the fix for this (once, hopefully soon, ready)
> be added to 0.6.1 as https://issues.apache.org/jira/browse/MINIFICPP-960
>
> Best,
> Daniel
>
> On Sat, 6 Jul 2019 at 17:21, Arpad Boda  wrote:
>
> > As a result of this vote MiNiFi C++ 0.6.1 is going to be released soon
> with
> > the following scope:
> > https://issues.apache.org/jira/browse/MINIFICPP-786
> > https://issues.apache.org/jira/browse/MINIFICPP-933
> > https://issues.apache.org/jira/browse/MINIFICPP-919
> >
> > I will do the RM duties.
> >
> > Regards,
> > Arpad
> >
> > On Thu, Jun 27, 2019 at 3:00 PM Aldrin Piri 
> wrote:
> >
> > > I agree with 786 for sure.  I apologize, I may have interpreted your
> > > initial response a bit literally with regards to the "feature bearing"
> > > JIRAs.  Just wanted to clarify that new features would not be in scope
> > for
> > > a fix version release, but in terms of adjusting the expected
> > > functionality, totally onboard with that.
> > >
> > > On Thu, Jun 27, 2019 at 8:47 AM Jeremy Dyer  wrote:
> > >
> > > > Completely agree but isn’t MINIFICPP-786 an issue we could include as
> > > part
> > > > of that?
> > > >
> > > > On Wed, Jun 26, 2019 at 6:35 PM Aldrin Piri 
> > > wrote:
> > > >
> > > > > I think the intent is for this to be a fix release and wouldn’t
> > include
> > > > > any new features.
> > > > >
> > > > > > On Jun 26, 2019, at 17:47, Jeremy Dyer  wrote:
> > > > > >
> > > > > > +1 it’s time and lots of feature bearing JIRAs have been resolved
> > > > > >
> > > > > > I do agree with with Arpad however on the inclusion of
> > MINIFICPP-786
> > > > > >
> > > > > >> On Wed, Jun 26, 2019 at 5:37 PM Arpad Boda 
> > > wrote:
> > > > > >>
> > > > > >> Happy to take RM roles as well.
> > > > > >>
> > > > > >>> On Wed, Jun 26, 2019 at 10:30 AM Arpad Boda <
> ab...@cloudera.com>
> > > > > wrote:
> > > > > >>>
> > > > > >>> +1.
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>> As this release seems to be a Windows-focused, I would also
> > > consider
> > > > > >>> adding https://issues.apache.org/jira/browse/MINIFICPP-786
> > > > > >>>
> > > > > >>> On Tue, Jun 25, 2019 at 11:53 PM Marc Parisi <
> > phroc...@apache.org>
> > > > > >> wrote:
> > > > > >>>
> > > > > >>>> Hi Everyone,
> > > > > >>>>
> > > > > >>>> I wanted to discuss releasing Apache NiFi MiNiFi C++ 0.6.1
> with
> > > some
> > > > > >>>> important bug fixes. We've had a few issues that impact
> Windows
> > > > users
> > > > > >> and
> > > > > >>>> TLS with Raw Site To Site [1,2]. With these bugs addressed I
> > think
> > > > we
> > > > > >>>> should look to releasing 0.6.1.
> > > > > >>>>
> > > > > >>>> I would like to scope this bug fix release to only critical
> and
> > > > > blocker
> > > > > >>>> tickets found after 0.6.0. Let me know what you think or if
> you
> > > > think
> > > > > >>>> anything else should be included that is critical to user
> > > > operations.
> > > > > >>>>
> > > > > >>>>  My time is pretty fragmented but will try my best to take on
> RM
> > > > > duties
> > > > > >>>> unless someone would like to try their hand at it.
> > > > > >>>>
> > > > > >>>>   Thanks,
> > > > > >>>>   Marc Parisi
> > > > > >>>>
> > > > > >>>> [1] https://issues.apache.org/jira/browse/MINIFICPP-933
> > > > > >>>> [2] https://issues.apache.org/jira/browse/MINIFICPP-919
> > > > > >>>>
> > > > > >>>
> > > > > >>
> > > > >
> > > >
> > >
> >
>

[DISCUSS] Apache NiFi MiNiFi C++ 0.6.1

[Marc Parisi]

Hi Everyone,

I wanted to discuss releasing Apache NiFi MiNiFi C++ 0.6.1 with some
important bug fixes. We've had a few issues that impact Windows users and
TLS with Raw Site To Site [1,2]. With these bugs addressed I think we
should look to releasing 0.6.1.

 I would like to scope this bug fix release to only critical and blocker
tickets found after 0.6.0. Let me know what you think or if you think
anything else should be included that is critical to user operations.

  My time is pretty fragmented but will try my best to take on RM duties
unless someone would like to try their hand at it.

   Thanks,
   Marc Parisi

[1] https://issues.apache.org/jira/browse/MINIFICPP-933
[2] https://issues.apache.org/jira/browse/MINIFICPP-919

Re: libminifi

[Marc Parisi]

Eric,

You could use LibMiNiFi as a library if that suits your purposes, but the
API is built in a way that lends itself to support an agent with its
various components ( repositories, threadpools, command and control, etc )

If you have small processes that are purpose built please take a look at
NaNoFi, which is a C API whose sole focus is embedding key control and data
delivery mechanisms into your software. There are some examples here [1].
If your goal is to transmit files or data to Apache NiFi, examples cover
that [2] that are a bit simpler than using LibMiNiFi. If you were to use
LibMiNiFi you may find yourself disabling components, but with NaNoFi you
build what you need. Let us know if you have any questions!

Thanks,
Marc

[1] https://github.com/apache/nifi-minifi-cpp/tree/master/nanofi/examples
[2]
https://github.com/apache/nifi-minifi-cpp/blob/master/nanofi/examples/transmit_flow.c
/
https://github.com/apache/nifi-minifi-cpp/blob/master/nanofi/examples/transmit_payload.c

On Sun, Jun 16, 2019 at 5:10 PM Eric Berryman 
wrote:

> Hello,
>
> I noticed the libminifi directory in the minifi-cpp repo. I was wondering
> if this means I could use minifi as a library, to send data to nifi?
> (Instead of running an agent) This would work very well for me with my use
> case. I have many (order of hundreds) small processes written in c/c++,
> that is our distributed control system. Our code has a module system, which
> I'm hoping could be use to extend to include exporting information to nifi
> with libminifi used as a library.
>
> Thank you!
> Eric
>

Re: [ANNOUNCE] New Apache NiFi PMC member Peter Wicks

[Marc Parisi]

Congrats!

On Thu, May 30, 2019, 2:58 PM Jeff  wrote:

> Welcome to the PMC, Peter!  Congrats!
>
> On Thu, May 30, 2019 at 2:45 PM Tony Kurc  wrote:
>
> > Congratulations Peter!!
> >
> > On Thu, May 30, 2019 at 11:21 AM Aldrin Piri  wrote:
> >
> > > NiFi Community,
> > >
> > > On behalf of the Apache NiFi PMC, I am pleased to announce that Peter
> > Wicks
> > > has accepted the PMC's invitation to join the Apache NiFi PMC.
> > >
> > > Peter's contributions have been plentiful in code, community, reviews
> and
> > > discussion after becoming a committer in November 2017.  His impact
> > across
> > > NiFi has lead to improvements surrounding Kerberos, GetFile, ListFile,
> > > Clustering, Node Offload, Recordset Writers, HDFS, and Database related
> > > processors among others.
> > >
> > > Thank you for all your contributions and welcome to the PMC, Peter!
> > >
> > > --aldrin
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Arpad Boda

[Marc Parisi]

Congratulations!

On Thu, May 23, 2019 at 9:23 AM Aldrin Piri  wrote:

> On behalf of the Apache NiFI PMC, I am very pleased to announce that Arpad
> has accepted the PMC's invitation to become a committer on the Apache
> NiFi project.
> We greatly appreciate all of Arpad's hard work and generous contributions
> to the project. We look forward to his continued involvement in the
> project.
>
> Arpad has been highly involved in the MiNiFi C++ codebase providing
> contributions covering everything from code cleanup, tests, and new
> features.  Arpad has been an active reviewer, contributor to JIRAs and
> aided in verification of releases across the NiFi project.  Thank you for
> all your efforts!
>
> Welcome and congratulations!
>
> --aldrin
>

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3.0

[Marc Parisi]

+1 Bryan,
   Followed the release helper performing signature/hash verification,
build, and basic verification.
   Thanks,
   Marc

On Thu, May 2, 2019 at 11:21 AM Matt Gilman  wrote:

> +1 binding
>
> Ran through release helper.
>
> Noticed one of the changes bumps the maven version to 3.1.1. Does this
> affect our minimum maven version needed to build? If so, we should be sure
> to update our readme which still references 3.1.0.
>
> Thanks for RMing Bryan!
>
> Matt
>
> On Thu, May 2, 2019 at 10:49 AM Aldrin Piri  wrote:
>
> > +1, binding
> >
> > notes:
> > signature and hashes looked good
> > build and contrib check good
> > performed build of NiFi using generated NAR and didn't notice any
> > peculiarities with typical operations.  NARs included the anticipated
> > descriptor file and its contents looked good
> >
> >
> >
> > On Thu, May 2, 2019 at 10:29 AM Kevin Doran  wrote:
> >
> > > +1 (binding)
> > >
> > > Ran through the steps in the release helper guide and verified the new
> > > metadata files are being written to the generated in NARs.
> > >
> > > Thanks for RM'ing, Bryan!
> > >
> > > On Tue, Apr 30, 2019 at 12:03 PM Bryan Bende 
> wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > > NiFi NAR Maven Plugin 1.3.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1142
> > > >
> > > > The Git tag is nifi-nar-maven-plugin-1.3.0-RC1
> > > > The Git commit ID is 84b66de25e5f1c0df66a4c8a0d1cbf00390aae18
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=84b66de25e5f1c0df66a4c8a0d1cbf00390aae18
> > > >
> > > > Checksums of nifi-nar-maven-plugin-1.3.0-source-release.zip:
> > > > SHA256:
> > ff4ba1879e4b10bf4e8808363438f8082508e60b7539c9c32a5097982e470f3c
> > > > SHA512:
> > >
> >
> 8b15553f5f4a5469f514a7d84c924f4ae27d3a0cc029217eb42923136e13e1074df4f1bccc80ef0def6b59b10dd85932a5ce2b93aaf918385b7798719518ad56
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/bbende.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 5 issues were closed/resolved for this release:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12340213
> > > >
> > > > Release note highlights can be found here:
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > > > Then please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-nar-maven-plugin-1.3.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > >
> >
>

Re: Apache JIRA contributor access

[Marc Parisi]

József,
  Thank you for your interest. You are now a contributor and should be able
to self assign. Please let me know if you have any issues. Thanks!

On Fri, Apr 12, 2019 at 11:41 AM József Kett  wrote:

> Hi,
>
> I would like to get contributor access to Apache Nifi and/or NiFi MiNiFi
> C++ on JIRA. Can you please add me to contributor list? My username is
> 'Kett'.
>
> Thanks,
> József
>

[ANNOUNCE] Apache NiFi MiNiFi C++ 0.6.0 release

[Marc Parisi]

The Apache NiFi team would like to announce the release of Apache NiFi MiNiFi
C++ 0.6.0.

MiNiFi—a subproject of Apache NiFi—is a complementary data collection
approach that supplements the core tenets of NiFi in dataflow management,
focusing on the collection of data at the source of its creation.

Specific goals for the initial thrust of the MiNiFi effort comprise:

   - Small size and low resource consumption
   - Central management of agents
   - Generation of data provenance (full chain of custody of information)
   - Integration with NiFi for follow-on dataflow management


Highlights of 0.6.0 release include:

   - Began structuring library known as NanoFi
   - Added several processors (WEL Reader, Sensor Readers, and HashContent
   to name a few )
   - Added JNI Support to run NiFi processors in MiNiFi C++ flows,  when
   Java is allowed and enabled
   - Added Support for Natively written Python processors
   - Added a CoAP package for Command and Control
   - Windows support through Visual Studio with appveyor build
   - Added docker builds for centos, debian, fedora,  u16, and u18
   - Improved static build process across distros


More details on Apache NiFi - MiNiFi C++ can be found here:
https://nifi.apache.org/minifi

The release artifacts can be downloaded from here:
https://nifi.apache.org/minifi/download.html

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12343363

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI
/Release+Notes#ReleaseNotes-Versioncpp-0.6.0

Thank you
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.6.0

[Marc Parisi]

Apache NiFi Community,

I am pleased to announce that the 0.6.0 release of Apache NiFi MiNiFi C++
passes with
 4 +1 (binding) votes
 1 +1 (non-binding) votes
 0 0 votes
 0 -1 (binding) votes
 0 -1 (non-binding) votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
https://lists.apache.org/thread.html/aded61a15720fa12880971c641e51383976f8ebc2c6dde2fbe480ed9@%3Cdev.nifi.apache.org%3E

Re: Apache NiFi MiNIFI C++ 0.6.0 RC2 Release Helper Guide

[Marc Parisi]

The E-mail I sent moments ago has an incorrect subject line. This release
helper guide is for the second release candidate ( RC2), not RC1. I
apologize for the error.

Thanks,
Marc

On Tue, Mar 19, 2019 at 12:52 PM Marc Parisi  wrote:

> Hello Apache NiFi community,
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
> # Download latest KEYS file:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> # Import keys file:
> gpg --import KEYS
>
>
> # Pull down nifi-minifi-cpp-0.6.0 source release artifacts for review:
>
> wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz
> wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.asc
> wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.sha256
> wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.sha512
>
> # Verify the signature
> gpg --verify nifi-minifi-cpp-0.6.0-source.tar.gz.asc
>
> # Verify the hashes (sha256, sha512) match the source and what was
> provided in the vote email thread
> sha256sum nifi-minifi-cpp-0.6.0-source.tar.gz
> sha512sum nifi-minifi-cpp-0.6.0-source.tar.gz
>
> # Untar and gzip nifi-minifi-cpp-0.6.0-source.tar.gz
> tar -xzf nifi-minifi-cpp-0.6.0-source.tar.gz
>
> # Verify the build works including release audit tool (RAT) checks
> cd nifi-minifi-cpp-0.6.0-source
> mkdir build && cd build && cmake .. && make package make test && make
> linter
>
> # Alternatively, you may run bootstrap.sh which is a menu guided
> configuration to configure your system to build MiNiFi C++
> cd nifi-minifi-cpp-0.6.0-source
> ./bootstrap.sh
>
> # Verify the contents contain a good README, NOTICE, and LICENSE.
>
> # Verify the git commit ID is correct
>
> # Verify the RC was branched off the correct git commit ID
>
> # Look at the resulting convenience binary as found in
>
> # Make sure the README, NOTICE, and LICENSE are present and correct
>
> # Run the resulting convenience binary and make sure it works as expected
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
> Thank you for your time and effort to validate the release!
>

[VOTE] Release Apache NiFi MiNiFi C++ 0.6.0 (RC2)

[Marc Parisi]

Hello Apache NiFi community,

I am pleased to call this vote for the source release of Apache NiFi MiNiFi
C++ 0.6.0

The source tar.gz, including signatures, digests, and convenience binaries.
can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/

The Git tag is minifi-cpp-0.6.0-RC2
The Git commit ID is 28ade6cf75e8a0ccce78699f147f4ad9baaf70c2
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=

28ade6cf75e8a0ccce78699f147f4ad9baaf70c2

Checksum of nifi-minifi-cpp-0.6.0-source.tar.gz:
SHA256: 65c5ecf4b8ce807e982ed4dcb11472f574f62e66bfeeaa3348b0852c926175c3
SHA512:
4c53275b6b595fe1a17f6ad54a4aaa831b45044f3f8a5ad204475d3beb8fde441fc28d4a385d8804ed28f7934e37d45a01ab130b5241baa414a7c788f23e4451

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/phrocker.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

142 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12343363

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.6.0

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build
from source, and test.  The please vote:

[ ] +1 Release this package as nifi-minifi-cpp-0.6.0
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Apache NiFi MiNIFI C++ 0.6.0 RC1 Release Helper Guide

[Marc Parisi]

Hello Apache NiFi community,

Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
gpg --import KEYS


# Pull down nifi-minifi-cpp-0.6.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0-rc2/nifi-minifi-cpp-0.6.0-source.tar.gz.sha512

# Verify the signature
gpg --verify nifi-minifi-cpp-0.6.0-source.tar.gz.asc

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
sha256sum nifi-minifi-cpp-0.6.0-source.tar.gz
sha512sum nifi-minifi-cpp-0.6.0-source.tar.gz

# Untar and gzip nifi-minifi-cpp-0.6.0-source.tar.gz
tar -xzf nifi-minifi-cpp-0.6.0-source.tar.gz

# Verify the build works including release audit tool (RAT) checks
cd nifi-minifi-cpp-0.6.0-source
mkdir build && cd build && cmake .. && make package make test && make linter

# Alternatively, you may run bootstrap.sh which is a menu guided
configuration to configure your system to build MiNiFi C++
cd nifi-minifi-cpp-0.6.0-source
./bootstrap.sh

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.6.0 (rc1)

[Marc Parisi]

Hi Everyone,
  We're canceling RC-1. It seems that we have some temporary files in the
docker source directory. This was an oversight on my part, and in an effort
to keep
the source release pristine,  I will clean these up and send out another
RC. It will have the same commit tag and convenience binaries, but I will
update the source tarball and the corresponding hashes.

   Apologies for the hiccup!

   There is a ticket to address this, but since these files are ignored by
git it is slated for the next release (0.7.0) [1].


[1] https://issues.apache.org/jira/browse/MINIFICPP-778

On Mon, Mar 18, 2019 at 9:17 PM Marc Parisi  wrote:

> Hello Apache NiFi community,
>
> I am pleased to call this vote for the source release of Apache NiFi
> MiNiFi C++ 0.6.0
>
> The source tar.gz, including signatures, digests, and convenience
> binaries. can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/
> <https://repository.apache.org/content/repositories/orgapachenifi->
>
> The Git tag is minifi-cpp-0.6.0-RC1
> The Git commit ID is 38fd03d4cf6e5a78af7f73c822fc531b2d563bd0
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=38fd03d4cf6e5a78af7f73c822fc531b2d563bd0
>
> Checksum of nifi-minifi-cpp-0.6.0-source.tar.gz:
> SHA512:
> d61d95abe6dfaade010940833b78c1f07ded9dc7bb1559431369e1fd65375e9f5e40047d6773a0b6899a365b7b82ce00cd536871ce5102960c62086e799779bb
> SHA256: b93ac59553ce113241e335aa02dd9162cf1d072a04d19fc75987765790247667
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/phrocker.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 141 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12343363
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.6.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test.  The please vote:
>
> [ ] +1 Release this package as nifi-minifi-cpp-0.6.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because because...
>

Apache NiFi MiNIFI C++ 0.6.0 RC1 Release Helper Guide

[Marc Parisi]

Hello Apache NiFi community,

Please find the associated guidance to help those interested in
validating/verifying the release so they can vote.

# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
gpg --import KEYS


# Pull down nifi-minifi-cpp-0.6.0 source release artifacts for review:

wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/nifi-minifi-cpp-0.6.0-source.tar.gz
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/nifi-minifi-cpp-0.6.0-source.tar.gz.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/nifi-minifi-cpp-0.6.0-source.tar.gz.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/nifi-minifi-cpp-0.6.0-source.tar.gz.sha512

# Verify the signature
gpg --verify nifi-minifi-cpp-0.6.0-source-release.zip.asc

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
sha256sum  nifi-minifi-cpp-0.6.0-source.tar.gz
sha512sum nifi-minifi-cpp-0.6.0-source.tar.gz

# Untar and gzip nifi-minifi-cpp-0.6.0-source.tar.gz

# Verify the build works including release audit tool (RAT) checks
cd nifi-minifi-cpp-0.6.0
mkdir build && cd build && cmake .. && make package make test && make linter

# Alternatively, you may  run bootstrap.sh which is a menu guided
configuration
cd nifi-minifi-cpp-0.6.0
./bootstrap.sh

# Verify the contents contain a good README, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in

# Make sure the README, NOTICE, and LICENSE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

Thank you for your time and effort to validate the release!

[VOTE] Release Apache NiFi MiNiFi C++ 0.6.0 (rc1)

[Marc Parisi]

Hello Apache NiFi community,

I am pleased to call this vote for the source release of Apache NiFi MiNiFi
C++ 0.6.0

The source tar.gz, including signatures, digests, and convenience binaries.
can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.6.0/


The Git tag is minifi-cpp-0.6.0-RC1
The Git commit ID is 38fd03d4cf6e5a78af7f73c822fc531b2d563bd0
https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=38fd03d4cf6e5a78af7f73c822fc531b2d563bd0

Checksum of nifi-minifi-cpp-0.6.0-source.tar.gz:
SHA512:
d61d95abe6dfaade010940833b78c1f07ded9dc7bb1559431369e1fd65375e9f5e40047d6773a0b6899a365b7b82ce00cd536871ce5102960c62086e799779bb
SHA256: b93ac59553ce113241e335aa02dd9162cf1d072a04d19fc75987765790247667

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/phrocker.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

141 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12343363

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.6.0

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build
from source, and test.  The please vote:

[ ] +1 Release this package as nifi-minifi-cpp-0.6.0
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Re: jni with Apache Nifi

[Marc Parisi]

Brett,
  You can take a look at what we do in Apache NiFi MiNiFi C++ --
https://github.com/apache/nifi-minifi-cpp/tree/master/extensions/jni

  In this package you can see the Java code that links in the logger.

   In the class we use to launch NiFI processors [1] we first obtain the
logger class reference from the class loader, after which we set a
reference to the pointer (in our Java object ) that allows us to return the
ComponentLogger with ours from MiNiFi C++. This enables components within
NiFi to log to MiNiFI C++, and for us to access loggers if need be.

   Hope this helps.

[1]
https://github.com/apache/nifi-minifi-cpp/blob/master/extensions/jni/ExecuteJavaProcessor.cpp#L103

   Let me know if you have any other questions.
   Marc Parisi

On Wed, Mar 6, 2019 at 4:44 PM Brett Tiplitz 
wrote:

> I'm trying to make a call from C++ into the Apache Nifi Logger.  I see an
> abstract logger class, but nothing static.  I also look at all the class
> methods, and nothing is appearing to be an external callable method.  Any
> suggestions?
>
> brett
>

[DISCUSS] Apache NiFi MiNiFi C++ 0.6.0

[Marc Parisi]

Hello everyone,
  I wanted to discuss releasing Apache NiFi MiNiFi C++ 0.6.0 in the coming
week or two. We have some exciting new features and even more exciting bug
fixes.

   This release will see the growth of a sub-component called nanofi, which
will be an easily consumable library that enables integration within
existing applications. Additionally, we've introduced a new C2 CoAP
protocol, the ability to write and execute custom native Python processors
in flows, and a JNI link that enables running Java processors from within a
much smaller resource footprint in MiNiFI C++ -- closing gaps and enabling
feature sets. This release will also see the introduction of Windows builds
and various fixes that will improve the user experience.

   As with all releases, these feature sets can be customized for use
cases/deployments.

   If everyone is amenable to a release, I will RM unless anyone would like
to take those duties.

   Best Regards,
   Marc Parisi

Re: Opinions on Assembly target location

[Marc Parisi]

Thank you for your replies. My goal was to have that shared ownership as
Bryan suggested; however, the simplicity of bootstrapping these efforts
within Apache NiFi MiNiFi C++, controlling dependencies, and overall ease
of use by maintainers has led me to close the PR and place this assembly in
MiNiFi C++. This enables the builder to package all necessary components
within the produced archive and have access to Java processors within
MiNiFI C++( they must purposefully enable this feature ).  Just wanted to
close the loop.
Thank you for your consideration

On Wed, Feb 27, 2019 at 12:52 PM Bryan Bende  wrote:

> I think this situation is sort of analogous to some other scenarios we
> have run into, such as the integrations between NiFi and stream
> processing.
>
> For example, the storm and spark integration lives in NiFi's code
> base, and NiFi is responsible for determining if a new version of
> those APIs is available, updating the dependency, and resolving any
> necessary code changes.
>
> The Flink and Apex integration lives in each of those respective code
> bases, so if Flink changes all of their APIs, they will be forced to
> update the NiFi Flink source/sink in order to make their build pass.
>
> I can see value in either approach. If we consider the JNI stuff to be
> a more generic capability, then I think I lean towards NiFi owning it.
>
> Even with that, MiNiFi will still be dependent on some version of
> whatever JNI artifacts NiFi produces, so MiNiFi would still have
> ownership over when to change that dependency and ensure that it still
> works properly in a given release of MiNiFi.
>
> On Wed, Feb 27, 2019 at 12:02 PM Arpad Boda  wrote:
> >
> > Hi,
> >
> > In my opinion, there is another question here to be answered: what
> version of NiFi NARs do we expect to work in MiNiFi?
> >
> > I see two different approaches here:
> > -#1) MiNiFi is compatible with a given NiFi version, like 1.9.0, NARs in
> that release work properly in MiNiFi.
> > In this case the tests belong to MiNiFi and NiFi there becomes a
> dependency -> the tests are required to pass when upgrading the dependency.
> > -#2) MiNiFi is compatible with master. This means that whatever we
> introduce in NiFi shouldn't break, so the tests more belong to NiFi.
> >
> > According to my experience preventing the merge of a breaking change is
> easier than fixing later, which would make me vote for #2, however this
> approach has a side effect, too: introducing a breaking change (that MiNiFi
> needs to adapt) becomes a huge pain, it's much easier in #1.
> >
> > Regards,
> > Arpad
> >
> > On 27/02/2019, 17:44, "Marc Parisi"  wrote:
> >
> > Hi ,
> >I've submitted a PR to Apache NiFi MiNiFi C++ that enables the
> project
> > to access and run NiFi processors. This requires that certain jars be
> > included to bootstrap that process long with a set of NARs from
> which we
> > will access the desired components. Effectively this means that a
> user can
> > run the current set of C++ processors alongside Java processors.
> >To facilitate this feature's use, I submitted a PR [1] to NiFi
> with that
> > assembles the appropriate JARs and a basic set of useful/necessary
> NARs.
> > I'd like opinions on where this should live. The options have been
> to place
> > it within Apache NiFi MiNIFi C++ ( specifically within the
> aforementioned
> > feature's build directory) as it only relates to that project and,
> perhaps
> > allowing us to more easily address problems...or as per the PR:
> placing it
> > in NiFi proper, hopefully building regression tests that notify us of
> > issues before a release.
> >
> >I've been wavering on the options and want community opinion. The
> end
> > goal in either case is that if/when a user builds with this
> functionality
> > we can deliver a package that runs out of the box. This can be done
> with
> > either approach.
> >
> > The net positive of placing it in NiFi as I see it: sense that
> it is an
> > official feature and perhaps notification before NiFi release or in
> > travis.  Side effects include: questioning if this belongs here,
> hair loss,
> > and perhaps a sudden loss of appetite.
> >
> > The net positive of isolating this within MiNIFi C++: cleaner end
> > solution, it's produced in the same place it's consumed, ability to
> notify
> > of problems in our CI and release process ( this could be viewed as a
> > negative too ? ).
> >
> > TL;DR:  Where feature Live?
> >
> > Any insight/opinions are appreciated. Thanks!
> >
> > [1] https://github.com/apache/nifi/pull/3330
> >
> >
>

Opinions on Assembly target location

[Marc Parisi]

Hi ,
   I've submitted a PR to Apache NiFi MiNiFi C++ that enables the project
to access and run NiFi processors. This requires that certain jars be
included to bootstrap that process long with a set of NARs from which we
will access the desired components. Effectively this means that a user can
run the current set of C++ processors alongside Java processors.
   To facilitate this feature's use, I submitted a PR [1] to NiFi with that
assembles the appropriate JARs and a basic set of useful/necessary NARs.
I'd like opinions on where this should live. The options have been to place
it within Apache NiFi MiNIFi C++ ( specifically within the aforementioned
feature's build directory) as it only relates to that project and, perhaps
allowing us to more easily address problems...or as per the PR: placing it
in NiFi proper, hopefully building regression tests that notify us of
issues before a release.

   I've been wavering on the options and want community opinion. The end
goal in either case is that if/when a user builds with this functionality
we can deliver a package that runs out of the box. This can be done with
either approach.

The net positive of placing it in NiFi as I see it: sense that it is an
official feature and perhaps notification before NiFi release or in
travis.  Side effects include: questioning if this belongs here, hair loss,
and perhaps a sudden loss of appetite.

The net positive of isolating this within MiNIFi C++: cleaner end
solution, it's produced in the same place it's consumed, ability to notify
of problems in our CI and release process ( this could be viewed as a
negative too ? ).

TL;DR:  Where feature Live?

Any insight/opinions are appreciated. Thanks!

[1] https://github.com/apache/nifi/pull/3330

Re: [VOTE] Release Apache NiFi 1.9.0 (rc2)

[Marc Parisi]

+1 ( binding )
 verified sigs and hashes.
 Built and tested with centos and u18, performing simple flow verification
with minifi and registry.



On Tue, Feb 19, 2019 at 9:09 AM Aldrin Piri  wrote:

> +1, binding
>
> signature good
> hashes looked good
> full build and tests looked good on macos 10.14 and Debian 9
> performed some simple flows pulling from registry
> verified site to site functionality
>
> On Tue, Feb 19, 2019 at 8:24 AM Laszlo Horvath 
> wrote:
>
> > +1 (non-binding)
> >
> > - Verified signature
> > - Verified hashes
> > - Verified the build and tests were successful
> > - Verified Git commit ID
> > - Binary starts as expected
> >
> > Regards,
> > Laszlo
> >
> > On 19/02/2019, 10:17, "Koji Kawamura"  wrote:
> >
> > +1 Release this package as nifi-1.9.0 (binding)
> >
> > - Verified signature and hashes
> > - Clean build & test passed
> > - Tested flows using standalone and secure cluster environments
> >
> > Thanks,
> > Koji
> >
> > On Mon, Feb 18, 2019 at 10:30 PM Denes Arvay 
> wrote:
> > >
> > > +1 Release this package as nifi-1.9.0 (non-binding)
> > >
> > > - Verified signature
> > > - Verified hashes
> > > - Verified that the RC was branched off the correct git commit ID
> > > - Build successful & tests pass (using mvn clean install
> > > -Pcontrib-check,include-grpc)
> > > - Started and tested with a simple flow
> > >
> > > (nit: the NOTICE files still contain copyright ...-2018)
> > >
> > > Best,
> > > Denes
> > >
> > > On Sun, Feb 17, 2019 at 4:50 AM Joe Witt 
> wrote:
> > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of
> > Apache NiFi
> > > > nifi-1.9.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found
> > at:
> > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1136
> > > >
> > > > The Git tag is nifi-1.9.0-RC2
> > > > The Git commit ID is 45bb53d2aafd6ec5cb6bb794b3f7f8fc8300a04b
> > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=45bb53d2aafd6ec5cb6bb794b3f7f8fc8300a04b
> > > >
> > > > Checksums of nifi-1.9.0-source-release.zip:
> > > > SHA256:
> > f8d2987a98903f0c00c50677f3a6ad361e417c6021f5179280cbe9ca838695da
> > > > SHA512:
> > > >
> > > >
> >
> 2e77c420f932514417693584b4708a534df398e344dac7c1471f55cc382b7493d73b10ebc0d9e58562eb989c1f0b72980d6d18a2555883267f0bc08f092f30fe
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/joewitt.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 160 issues were closed/resolved for this release:
> > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12344357
> > > >
> > > > Release note highlights can be found here:
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.0
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.0-rc2/
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> > items
> > > > including checking hashes, signatures, build
> > > > from source, and test. Then please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.9.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> >
> >
> >
> >
>

Re: [VOTE] Release Apache NiFi 1.8.0 (RC3)

[Marc Parisi]

+1 ( binding )

Ran through the helper guide, testing normal flows ( w and w/o secure comms
)

Thanks,
Marc

On Wed, Oct 24, 2018 at 2:05 AM Koji Kawamura 
wrote:

> +1 (binding)
>
> Ran through the release helper.
> No issue was found.
> Thanks for RM duties, Jeff!
>
> On Wed, Oct 24, 2018 at 1:42 PM James Wing  wrote:
> >
> > +1 (binding).  Ran though the release helper, tested the resulting
> binary.
> > Thank you for your persistence, Jeff.
> >
> >
> > On Mon, Oct 22, 2018 at 10:56 PM Jeff  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > > nifi-1.8.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1135
> > >
> > > The Git tag is nifi-1.8.0-RC3
> > > The Git commit ID is 98aabf2c50f857efc72fd6f2bfdd9965b97fa195
> > >
> > >
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=98aabf2c50f857efc72fd6f2bfdd9965b97fa195
> > >
> > > Checksums of nifi-1.8.0-source-release.zip:
> > > SHA256:
> 6ec21c36ebb232f344493a4aeb5086eed0c462c576e11a79abed8149bc8b65c3
> > > SHA512:
> > >
> > >
> 846aecd4eb497a3b7dee7d1911b02453b8162b6c87e39f3df837744a478212e2e3e3615921079d29c2804671f26ecd05b04ce46a4bb69e8911fc185e27be9c24
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/jstorck.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 209 issues were closed/resolved for this release:
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12343482
> > >
> > > Release note highlights can be found here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.8.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build
> > > from source, and test. Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.8.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
>

Re: [VOTE] Release Apache NiFi 1.8.0

[Marc Parisi]

+1 binding
  Did the usual release helper validation, tested with typical use cases
and test flows, with and without minifi in a secure env.

On Fri, Oct 19, 2018 at 1:09 AM Andrew Psaltis 
wrote:

> +1 non-binding
>
> Verified README.md, NOTICE, checksum, keys, Documentation for Load
> Balancing
> Ran various flows -- new features looking geat -- load balancing, JNDI JMS
>
> Great looking release.
>
> On Thu, Oct 18, 2018 at 12:59 PM Jeff  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > nifi-1.8.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1133
> >
> > The Git tag is nifi-1.8.0-RC1
> > The Git commit ID is 9b02d58626ca874ed2ed3e0bbe530512cfa0dbf8
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=9b02d58626ca874ed2ed3e0bbe530512cfa0dbf8
> >
> > Checksums of nifi-1.8.0-source-release.zip:
> > SHA256: 3ec90a7f153e507d7bba2400d6dafac02641d6f7afc7a954fed959191073ce21
> > SHA512:
> >
> >
> 8b9d944da1833bfb645f502107cab98a555e3b2a7602c5ff438407272c86defdeebe18625c5ad9dfb3f344397314569e97220a35f2438182a79a700caa90721e
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/jstorck.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 204 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12343482
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.8.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.8.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [VOTE] Release Apache NiFi Registry 0.3.0

[Marc Parisi]

+1 -- binding

   Validated sigs, checksums, built, and used within current integration
testing techniques in secure mode.

On Mon, Sep 24, 2018 at 9:16 AM Mark Payne  wrote:

> +1 (binding)
>
> Validated hashes, build with contrib-check. Started and ensured that
> registry is
> able to store and retrieve flow with load balancing information.
>
> Thanks for handling the RM duties this time around, Kevin!
>
> -Mark
>
>
> > On Sep 22, 2018, at 9:54 AM, Kevin Doran  wrote:
> >
> > Hello,
> >
> > I am pleased to call this vote for the source release of Apache NiFi
> > Registry 0.3.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> >
> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.3.0/
> >
> > The Git tag is nifi-registry-0.3.0-RC1
> > The Git commit ID is 2fef9fac2b627ee1f3428b07019b333c68f65f2d
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=2fef9fac2b627ee1f3428b07019b333c68f65f2d
> >
> > Checksums of nifi-registry-0.3.0-source-release.zip:
> > SHA1:   4340068ef7e3ba099f614b86be4d2d77016845d9
> > SHA256: c0a51f6b5855202993daa808015ddf26466843f3bc5727333f44661099c2ad5b
> > SHA512:
> efc9882511eaccca4cc83117f5a870859f80b3667d8d3d9bf6e1fec9a1e4d1f37abee4476aaa28245468eca0eec30a3e84eba8e547a0fc1a97fdf6c289ab8b96
> >
> > Release artifacts are signed with the following key:
> > Fingerprint = C09B A891 AED4 5B8C 2C23  1AFE 1FB6 6A91 F71B 6207
> > Available at:
> > https://people.apache.org/keys/committer/kdoran.asc
> > https://pgp.mit.edu/pks/lookup?op=get&search=0x1FB66A91F71B6207
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> >
> > 15 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343483&styleName=Html&projectId=12320920
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-registry-${VERSION}
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: Accumulo processors

[Marc Parisi]

Hey Mike,
  I recall looking at Mark's PR in May and believe it fit the bill for a
processor looking to live ingest data into Accumulo. Just be cautious of
minor and major compaction storms that may cause backpressure. Bulk load is
also possible -- and probably even easier with the record-oriented paradigm
-- but this is a great step.

   If you have a relatively large batch size and want to reduce the number
of mutations ( keep in mind internally the batch writer will make a copy of
that mutation ), there may be some benefit in reusing *mutation* [1] if
those puts are all within the same or a small set of rows within a table. I
don't suspect this will be a limiting factor for most, so it probably
depends on your situation.

[1]
https://github.com/apache/nifi/commit/114c8578e097c338b44d31e38454b199f2bb2660#diff-b68a6e83fae66bb7f1617ade75661fa4R243



On Mon, Sep 17, 2018 at 3:43 PM Mike Thomsen  wrote:

> David,
>
> Any progress? Been flirting with the idea of looking at Accumulo and wanted
> to sync up.
>
> Thanks,
>
> Mike
>
> On Sun, May 27, 2018 at 5:06 PM DAVID SMITH
>  wrote:
>
> > Ok, thanks I will keep that in mind when I (or whoever on my team writes
> > these) get to a point where we would like a review before trying to
> submit
> > back to the OS.
> > Dave
> >
> >
> > On Sunday, 27 May 2018, 21:51, Mike Thomsen 
> > wrote:
> >
> >
> >  If you do a PR, ping @joshelser. He works on HBase and Accumulo and
> > mentioned to me that he might be up for a code review on the Accumulo
> > processors.
> >
> > On Sun, May 27, 2018 at 4:38 PM DAVID SMITH
> >  wrote:
> >
> > > Mike
> > > Thanks for the suggestion I will certainly have a look at the HBase
> code,
> > > I'm not really familiar with Accumulo, I am currently reading the docs
> on
> > > the apache web site.
> > > Dave
> > >
> > >
> > >On Sunday, 27 May 2018, 21:25, Mike Thomsen  >
> > > wrote:
> > >
> > >
> > >  Dave,
> > >
> > > I don't know how far along Mark's code is, but you might find some
> useful
> > > code you can borrow from the HBase commit(s) that added visibility
> label
> > > support. For example, there is code for handling visibility labels w/
> > > PutHBaseRecord that might be reusable if you want to create a put
> record
> > > processor for Accumulo. It won't help you with the Accumulo APIs, but
> it
> > > could provide useful strategies for how to identify and assign labels
> > from
> > > user input.
> > >
> > > On Sun, May 27, 2018 at 3:14 PM DAVID SMITH
> > >  wrote:
> > >
> > > > Mark
> > > > Thanks for the link, I have downloaded the code from Github, it will
> > be a
> > > > good basis to start with.
> > > > Many thanksDave
> > > >
> > > >
> > > >On Saturday, 26 May 2018, 20:22, Mark Payne  >
> > > > wrote:
> > > >
> > > >
> > > >  Hi Dave,
> > > >
> > > > I do have a branch in Github with the work that I had done:
> > > > https://github.com/apache/nifi/tree/NIFI-818
> > > > To be perfectly honest, though, I have absolutely no idea what state
> > the
> > > > code is in, if it's been tested, etc.
> > > > But you're welcome to take it and run with it, if you'd like.
> > > >
> > > > Thanks
> > > > -Mark
> > > >
> > > >
> > > > On May 26, 2018, at 12:05 PM, davidrsmith <
> davidrsm...@btinternet.com
> > > > .INVALID> wrote:
> > > >
> > > > Hi
> > > >
> > > > A team at work has a need to interface with accumulo, has anyone
> tried
> > > > this, I know a while ago Mark Payne raised nifi jira ticket 818 but
> as
> > > far
> > > > as I am aware this was never completed.
> > > > I would be grateful if anyone can help or point me in the direction
> of
> > > > Mark's code that will give us a start.
> > > >
> > > > Many thanks
> > > > Dave
> > > >
> > > >
> > > >
> > > >
> > > > Sent from Samsung tablet
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Jeremy Dyer

[Marc Parisi]

Congrats Jeremy! Well deserved for you as well!

On Tue, Jul 31, 2018, 8:42 AM Pierre Villard 
wrote:

> Congrats Jeremy! Well deserved, thanks for all the work on the (Mi)NiFi
> projects (and the OAuth part under review)!
>
> 2018-07-31 14:36 GMT+02:00 Tony Kurc :
>
> > All,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Jeremy
> Dyer
> > has accepted the PMC's invitation to join the Apache NiFi PMC.
> >
> > Jeremy has been a long-time contributor to the project - across many
> > different parts of the project to include NiFi and and MiNiFi,
> contributing
> > code, reviews, release verification, and help on the mailing lists. He's
> > performed the challenging, detail oriented work of acting as a release
> > manager for both the Java and C++ versions of MiNiFi (0.5.0 of each).
> >
> > Congratulations Jeremy and well deserved!
> >
> > Tony
> >
>

Re: [ANNOUNCE] New NiFi PMC member Kevin Doran

[Marc Parisi]

Congrats! Well deserved!

On Tue, Jul 31, 2018, 8:41 AM Pierre Villard 
wrote:

> Congrats Kevin, very well deserved, thanks for all your work on the NiFi
> projects!
>
> 2018-07-31 14:26 GMT+02:00 Tony Kurc :
>
> > NiFi Community,
> >
> > On behalf of the Apache NiFi PMC, I am pleased to announce that Kevin
> Doran
> > has accepted the PMC's invitation to join the Apache NiFi PMC.
> >
> > In addition to being a regular code contributor to the project for quite
> > some time, Kevin has been hard to miss on the mailing lists, especially
> on
> > NiFi Registry threads. We all appreciate his hard work getting releases
> > "out the door", helping verify releases and recently doing release
> manager
> > duty for the NiFi Registry 0.2.0.
> >
> > Please join us in congratulating and welcoming Kevin to the Apache NiFi
> > PMC.
> >
> > Tony
> >
>

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

[Marc]

+1 binding

Sorry for sending so late Jeremy, but I did verification late
Fridayjust forgot to send

 Built and ran test flows. Verified sigs and hashes. Looks good.

On Fri, Jun 29, 2018, 6:59 PM Andy LoPresto  wrote:

> +1, binding
>
> Verified all keys and checksums, ran through all the builds, verified
> tests and contrib-check, and the existence of LICENSE/NOTICE/README at
> appropriate locations. A couple minor points on the release process below
> (and some other non-blocking issues that I will open as Jiras).
>
> * Now that MD5 is deprecated, I believe we agreed to provide a SHA-512
> signature as well. The release guide should be updated to include this for
> next time.
> * The release helper should specify that LICENSE, NOTICE, and README are
> in minifi-assembly/target*/minifi-0.5.0-bin/minifi-0.5.0/*
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jun 29, 2018, at 8:29 AM, Aldrin Piri  wrote:
>
> Hi folks,
>
> I worked with Jeremy to resolve the discrepancy and we were able to get the
> commits/tag in question from the Maven release plugin pushed to the repo.
>
> The minifi-0.5.0-RC2 tag is correct in pointing to the source of the...
> source commit 58b8c598c0866c8f1200164ab14f3df0d632d522 which was initiated
> from the last commit on master, 05f516d3da33a0547ccfad342414504cdacd4a68.
>
> Links for reference:
> tag:
> * https://github.com/apache/nifi-minifi/tree/minifi-0.5.0-RC2
> *
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=shortlog;h=refs/tags/minifi-0.5.0-RC2
>
> RC2 branch commit:
> *
>
> https://github.com/apiri/nifi-minifi/commit/58b8c598c0866c8f1200164ab14f3df0d632d522
> *
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=58b8c598c0866c8f1200164ab14f3df0d632d522
>
> --aldrin
>
>
> On Fri, Jun 29, 2018 at 7:59 AM Jeff Zemerick 
> wrote:
>
> +1 non-binding
>
> Built and ran MiNiFi and C2 without issues.
>
> On Thu, Jun 28, 2018 at 3:59 PM Aldrin Piri  wrote:
>
> +1, binding
>
> comments:
> My vote is on the assumption there there was a slight mix up with tagging
> and it can be easily remedied.  The
> 05f516d3da33a0547ccfad342414504cdacd4a68
> points to the last commit and a snapshot version.  This is correct from
> where the release is started but does not capture the generated prepared
> release artifacts.  I believe if that is pushed and referenced, we will
> have what is packed in the source distribution, which is listed as 0.5.0,
> non-snapshot.
>
> signature and hashes looked good
> verified contrib, build, and tests of minifi, config-toolkit, and c2
>
> server
>
> verified transform functionality of config toolkit
> verified consumption of transformed config in minifi and its successful
> site to site transaction to nifi
> verified interaction with c2 server with a file based provider
>
> On Thu, Jun 28, 2018 at 1:19 PM Jeremy Dyer 
>
> wrote:
>
>
> Hello,
>
> I am pleased to call this vote for the source release of Apache NiFi
>
> MiNiFi
>
> minifi-0.5.0 RC2.
>
> The source zip, including signatures, digests, etc. can be found at:
> *
>
> https://repository.apache.org/content/repositories/orgapachenifi-1130/
>
> <
>
> https://repository.apache.org/content/repositories/orgapachenifi-1130/
>
> *
>
> The Git tag is minifi-0.5.0-RC2
> The Git commit ID is 05f516d3da33a0547ccfad342414504cdacd4a68
> *
>
>
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=05f516d3da33a0547ccfad342414504cdacd4a68
>
> <
>
>
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=05f516d3da33a0547ccfad342414504cdacd4a68
>
> *
>
> *
>
>
>
> https://github.com/apache/nifi-minifi/commit/05f516d3da33a0547ccfad342414504cdacd4a68
>
> <
>
>
>
> https://github.com/apache/nifi-minifi/commit/05f516d3da33a0547ccfad342414504cdacd4a68
>
> *
>
>
> wget
>
>
>
>
> https://repository.apache.org/content/repositories/orgapachenifi-1130/org/apache/nifi/minifi/minifi/0.5.0/minifi-0.5.0-source-release.zip
>
>
> Checksums of minifi-0.5.0-source-release.zip:
> SHA1: be624db030aedd5c249e58c4c57d55ca917cd6ea
> SHA256:
>
> 1f96ca7d8c2f52f9c15dad532065163f14cb01a2edbc783d4faa33656ff5ab88
>
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jeremydyer.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 16 issues were closed/resolved for this release:
> *
>
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319921&version=12342658
>
> <
>
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319921&version=12342658
>
> *
>
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/MINIFI/Release+
> Notes#ReleaseNotes-Version0.5.0
>
> The vote will be open until 2:00PM EDT, 1 July 2018.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, si

Re: [VOTE] Release Apache NiFi 1.7.0

[Marc]

+1 binding

Tested my traditional flows with and without MiNiFi. Ran through the
release guide. Looks great. Props to Andy for doing this while at a
conference at which he presented.

On Fri, Jun 22, 2018, 6:18 AM Pierre Villard 
wrote:

> +1 binding
>
> Went through the release helper guide
> Tested secured/unsecured standalone, secured/unsecured clustered NiFi
> deployments + NiFi Registry
> Tested some new features of this release: XML reader/writer, Hadoop/Hive 3,
> monitoring RTs, cloud stuff.
> All looks good!
>
> Thanks Andy for taking care of the release and thanks to the community for
> all the great content in this release!
>
> Pierre
>
> 2018-06-22 7:33 GMT+02:00 Koji Kawamura :
>
> > +1 (binding)
> >
> > Verified things in release helper guide.
> > Tested that a NiFi flow created in old version can be used with 1.7.0.
> >
> > There are some component properties those have been renamed.
> > I listed such properties that I'm aware of, on the Migration Guidance
> page.
> > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> >
> > Thanks Andy for volunteering the Release Manager duties!
> >
> > Koji
> >
> >
> > On Thu, Jun 21, 2018 at 11:44 PM, Otto Fowler 
> > wrote:
> > > +1
> > > builds, tests, contrib
> > > checksum, signing
> > > tag checkout by commit and diff
> > >
> > >
> > >
> > > On June 20, 2018 at 03:16:47, Andy LoPresto (alopre...@apache.org)
> > wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > nifi-1.7.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1127
> > >
> > > and
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.7.0
> > >
> > > The Git tag is nifi-1.7.0-RC1
> > > The Git commit ID is 99bcd1f88dc826f857ae4ab33e842110bfc6ce21
> > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 99bcd1f88dc826f857ae4ab33e842110bfc6ce21
> > >
> > > Checksums of nifi-1.7.0-source-release.zip:
> > > SHA1: 11086ef532bb51462d7e1ac818f6308d4ac62f03
> > > SHA256:
> b616f985d486af3d05c04e375f952a4a5678f486017a2211657d5ba03aaaf563
> > > SHA512:
> > > d81e9c6eb7fc51905d6f6629b25151fc3d8af7a3cd7cbc3aa03be390c056
> > 1858d614b62d8379a90fdb736fcf5c1b4832f4e050fdcfcd786e9615a0b5cc1d563d
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/alopresto.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 194 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12342979&projectId=12316020
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.7.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build
> > > from source, and test. Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.7.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because…
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > *alopresto.apa...@gmail.com *
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
>

Re: [VOTE] Release Apache NiFi Registry 0.2.0

[Marc]

+1 binding..

  Stepped through helper guide for verification and validation. Looks great!

On Mon, Jun 18, 2018, 4:18 AM Pierre Villard 
wrote:

> +1 binding,
>
> - Went through the release helper guide
> - Tested the hook mechanism
>
> All looks good to me. Thanks for the release management Kevin and to all
> the contributors!
>
> Pierre
>
> 2018-06-18 8:05 GMT+02:00 Koji Kawamura :
>
> > +1 (binding)
> >
> > - Run through Release Helper Guide
> > - Tested other database other than H2
> > - Tested Git persistence provider
> >
> > Few minor feedback:
> >
> > 1. Database user whose password is blank can not be used
> >
> > When I used HSQLDB, the default 'sa' user does not have password. If I
> > configure a blank password property, I got following error.
> > Work-around: create a user with password
> > Caused by: java.lang.IllegalStateException: nifi.registry.db.password
> > is required
> > at
> org.apache.nifi.registry.db.DataSourceFactory.createDataSource(
> > DataSourceFactory.java:78)
> > ~[na:na]
> >
> > 2. V2__Initial.sql uses 'TEXT' data type, which is not supported in some
> > DBMS
> >
> > While many databases such as MySQL, PostgreSQL, SQL Server and Oracle
> > ... etc support TEXT, it is not a standard data type and some other
> > database engines do not support it (e.g. HSQLDB).
> > Also, Microsoft docs mention that SQL Server may remove TEXT data type
> > in the future release.
> > https://docs.microsoft.com/en-us/sql/t-sql/data-types/ntext-
> > text-and-image-transact-sql?view=sql-server-2017
> >
> > V1__Initial.sql uses 'VARCHAR(4096)' instead. That can support more
> > databases.
> > After changing V2__Initial.sql to use VARCHAR, I was able to use HSQLDB.
> >
> >
> > Thanks,
> > Koji
> >
> > On Sun, Jun 17, 2018 at 9:13 PM, Jeff Zemerick 
> > wrote:
> > > +1 non-binding
> > >
> > > Ran through the release helper guide with no issues. Good stuff!
> > >
> > > On Sat, Jun 16, 2018 at 5:47 PM Andy LoPresto <
> > alopresto.apa...@gmail.com>
> > > wrote:
> > >
> > >> Sorry everyone,
> > >>
> > >> Committers can provide binding votes on technical discussions (such as
> > to
> > >> call for a release), but only PMC members can provide binding votes on
> > >> releases. This is an Apache policy.
> > >>
> > >> I’ll update the page on Monday to be a bit clearer on the distinction.
> > >>
> > >> Andy LoPresto
> > >> alopre...@apache.org
> > >> alopresto.apa...@gmail.com
> > >> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >>
> > >> > On Jun 16, 2018, at 14:34, Andy LoPresto <
> alopresto.apa...@gmail.com>
> > >> wrote:
> > >> >
> > >> > Abdelkrim,
> > >> >
> > >> > Thanks for validating the release and voting. Just to clarify, only
> > PMC
> > >> members and committers [1] can cast a “binding” vote. All other
> > community
> > >> members are welcome to cast a +1, 0, or -1 vote as well, but these are
> > >> “non-binding”. Thanks again.
> > >> >
> > >> > [1] http://nifi.apache.org/people.html
> > >> >
> > >> > Andy LoPresto
> > >> > alopre...@apache.org
> > >> > alopresto.apa...@gmail.com
> > >> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >> >
> > >> >> On Jun 16, 2018, at 14:23, Abdelkrim Hadjidj <
> > ahadj...@hortonworks.com>
> > >> wrote:
> > >> >>
> > >> >> +1 (binding)
> > >> >>
> > >> >> - Tested everything from the release helper and everything worked
> > fine
> > >> >> - Tested the GitFlowPersistenceProvider with Github, works fine
> > >> >> - The Switching from other Persistence Provider section of the
> Admin
> > >> Guide asks to move the H2 DB specified as nifi.registry.db.directory.
> In
> > >> the Registery 0.2, this property is set to "". So it doesn't apply
> when
> > you
> > >> start a Registry 0.2 with FilePersistenceProvider and migrate to Git
> > >> provider.
> > >> >> - This is not an issue, but it seems that there no way to migrate
> > >> previous flow file from File provider to Git provider, or from an
> > existing
> > >> Git provider with Git clone.
> > >> >>
> > >> >> Thanks
> > >> >>
> > >> >> On 6/16/18, 3:22 PM, "Bryan Bende"  wrote:
> > >> >>
> > >> >>+1 (binding) Release this package as nifi-registry-0.2.0
> > >> >>
> > >> >>- Ran through everything in the release helper and looked good,
> > few
> > >> minor
> > >> >>things Andy mentioned
> > >> >>- Tested upgrading an existing registry to 0.2.0 to test
> database
> > >> migration
> > >> >>- Tested basic event hook logging
> > >> >>- Ran secure NiFi with secure registry
> > >> >>
> > >> >>I also never saw the strange Maven output that Andy reported.
> > >> >>
> > >> >>Thanks for RM'ing!!
> > >> >>
> > >> >>
> > >> >>>On Sat, Jun 16, 2018 at 1:29 AM, Andy LoPresto <
> > >> alopre...@apache.org> wrote:
> > >> >>>
> > >> >>> +1, binding
> > >> >>>
> > >> >>> I:
> > >> >>> * verified all checksums and signatures
> > >> >>> * ran through the normal build process (tests and contrib-check)
> > >> >>> * verified the LICENSE, NOTICE, a

Re: [ANNOUNCE] New Apache NiFi Committer Sivaprasanna Sethuraman

[Marc]

Congrats Sivaprasanna!

On Wed, Jun 6, 2018 at 12:07 AM, Scott Aslan  wrote:
> Congrats!
>
> On Tue, Jun 5, 2018 at 9:28 PM, Andrew Psaltis 
> wrote:
>
>> Congratulations Sivaprasanna!
>>
>> On Tue, Jun 5, 2018 at 12:25 PM, Pierre Villard <
>> pierre.villard...@gmail.com
>> > wrote:
>>
>> > Congrats, well deserved!
>> >
>> > 2018-06-05 18:14 GMT+02:00 Mike Thomsen :
>> >
>> > > Congratulations, Sivaprasanna!
>> > >
>> > > On Tue, Jun 5, 2018 at 10:22 AM Bryan Bende  wrote:
>> > >
>> > > > Congrats! and thank you for your contributions to the NiFi community.
>> > > >
>> > > > On Tue, Jun 5, 2018 at 10:16 AM, Kevin Doran 
>> > wrote:
>> > > > > Congrats, Sivaprasanna!
>> > > > >
>> > > > > On 6/5/18, 10:09, "Tony Kurc"  wrote:
>> > > > >
>> > > > > On behalf of the Apache NiFI PMC, I am very pleased to announce
>> > > that
>> > > > > Sivaprasanna has accepted the PMC's invitation to become a
>> > > committer
>> > > > on the
>> > > > > Apache NiFi project. We greatly appreciate all of
>> Sivaprasanna's
>> > > > hard work
>> > > > > and generous contributions to the project. We look forward to
>> > > > continued
>> > > > >  involvement in the project.
>> > > > >
>> > > > > Sivaprasanna has been working with the community on the mailing
>> > > > lists, and
>> > > > > has a big mix of code and feature contributions to include
>> > features
>> > > > and
>> > > > > improvements to cloud service integrations like Azure, AWS, and
>> > > > Google
>> > > > > Cloud.
>> > > > >
>> > > > > Welcome and congratulations!
>> > > > >
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.5.0

[Marc]

Jeremy,
  +1 binding

  Thanks for generating the release!

   I verified sigs and checksums. Built on u18 and OSX.

  I ran unit/integration tests with ctest. Also ran a simple flow with
GetFile -> LogAttribute, but also includes two controller services for
battery monitoring and network management.

  Thanks,
  Marc


On Thu, May 31, 2018 at 8:39 PM, Jeremy Dyer  wrote:
> Hello Apache NiFi Community,
>
> I am pleased to call this vote for the source release of Apache NiFi MiNiFi
> C++, nifi-minifi-cpp-0.5.0.
>
> The source archive, signature, and digests can be located at:
>
> Source Archive:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz
>
> GPG armored signature:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.asc
>
> Source MD5:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.md5
>
> Source SHA1:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha1
>
> Source SHA256:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.5.0/nifi-minifi-cpp-0.5.0-source.tar.gz.sha256
>
> The Git tag is minifi-cpp-0.5.0-RC1
> The Git commit hash is 5f3b3973e37def4d8ed2753837986d121fd58322
> * 
> *https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322
> <https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=5f3b3973e37def4d8ed2753837986d121fd58322>*
> * 
> *https://github.com/apache/nifi-minifi-cpp/commit/5f3b3973e37def4d8ed2753837986d121fd58322
> <https://github.com/apache/nifi-minifi-cpp/commit/5f3b3973e37def4d8ed2753837986d121fd58322>*
>
> Checksums of nifi-minifi-cpp-0.5.0-source.tar.gz:
> MD5: 9ec230b9ac3004981000276015860c52
> SHA1: a9e3fe34ed25f9f1a840cd318845bcdb6fb622f1
> SHA256: 78b5bbd65d1e3484efafc02a882f99063e06b88e1694daff6c24aaa3066037dc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> 87 issues were closed/resolved for this release:
> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12342659
> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12342659>*
>
> Release note highlights can be found here:
> *https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.5.0
> <https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.5.0>*
>
> The vote will close 3 June at 9PM EST.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-minifi-cpp-0.4.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
> Thanks!

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0

[Marc]

Jeremy,
  All issues in 0.5.0 have been resolved. Thanks!

On Wed, May 23, 2018 at 4:00 PM, Jeremy Dyer  wrote:
>
>
>
>
>
>
>
> No problem. Let me know when you get that PR merged in and 
> I’ll kick off the release process
>
>
>
> Thanks - Jeremy Dyer
>
>
>
>
>
> On Wed, May 23, 2018 at 1:20 PM -0400, "Marc"  wrote:
>
>
>
>
>
>
>
>
>
>
> Jeremy,
>   Thanks for stepping up!
>
> Aldrin,
>   I moved one ticket over that should be in 0.5.0 for which a PR
> exists. Aside from that we should be good to go when that is merged.
>
> On Wed, May 23, 2018 at 11:15 AM, Andy Christianson
>  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>>> Sounds great and I think we've gotten some important changes into the
>>> codebase from when this first started.  Do we have all the
>>> appropriate/needed issues tagged for this release?
>>
>> I support this release.
>>
>> For this release, I would like to bring special attention to MINIFICPP-281,
>> which has been marked "RESOLVED." In order for that to work, whoever builds 
>> the
>> .tar.gz should build the binary with all static linking options enabled, 
>> which
>> will minimize dependencies on libraries which may only be on the packager's
>> system, while maximizing portability of the tarball release.
>>
>> Regards,
>>
>> Andy I.C.
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.22 (GNU/Linux)
>>
>> iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
>> P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
>> EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
>> ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
>> cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
>> tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
>> =WN7S
>> -END PGP SIGNATURE-
>>
>> Sent from ProtonMail, Swiss-based encrypted email.
>
>
>
>
>

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0

[Marc]

Jeremy,
  Thanks for stepping up!

Aldrin,
  I moved one ticket over that should be in 0.5.0 for which a PR
exists. Aside from that we should be good to go when that is merged.

On Wed, May 23, 2018 at 11:15 AM, Andy Christianson
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>> Sounds great and I think we've gotten some important changes into the
>> codebase from when this first started.  Do we have all the
>> appropriate/needed issues tagged for this release?
>
> I support this release.
>
> For this release, I would like to bring special attention to MINIFICPP-281,
> which has been marked "RESOLVED." In order for that to work, whoever builds 
> the
> .tar.gz should build the binary with all static linking options enabled, which
> will minimize dependencies on libraries which may only be on the packager's
> system, while maximizing portability of the tarball release.
>
> Regards,
>
> Andy I.C.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJbBYVvAAoJEG1+mBKNMpIDH9sH/jnbw3hqxBVSZcZwimy2bmEN
> P64YR3k6Q+OT2pCIp3e88aAHLLy3KUGlZiltp7viiAiNIcHFAmEkbUfpsDEZB6On
> EyZJMV1NhEx3zDgapfhY3BUcarOgOjL77ZcVCuw3OU0LAkZFrXxG7Ok9YTY2smP8
> ve4Geck/O8aCtGL5hnNHecJGrm7KsVKbpUeutvwMMTLMNOPwv7ukxLp0o6QufR54
> cA0nIPJmLrbuCOWWJzSAzLXHu3Wzox9UQ9htNOHgqmzYCAEpMDZrHGE5xJs9K3Iy
> tLVRebJdQfvH+woKWzmwsqrgf3mSoY2iohza/46Tu3+OvETvVtS44RnFz3paKek=
> =WN7S
> -END PGP SIGNATURE-
>
> Sent from ProtonMail, Swiss-based encrypted email.

Re: [DISCUSS] Apache NiFi MiNiFi C++ 0.5.0

[Marc]

Reviving this thread -- Sorry for the delay. I will start the release
process with the completion of [1], likely in the next few days or
early next week. I will take RM duties unless someone else would like
to take that opportunity.

[1] https://issues.apache.org/jira/browse/MINIFICPP-457

Thanks,
Marc

On Sun, Feb 18, 2018 at 9:17 AM, Joe Witt  wrote:
> sounds good!
>
> On Feb 18, 2018 9:15 AM, "Kevin Doran"  wrote:
>
>> Hi Marc,
>>
>> Thanks for kicking off this discuss thread. I agree we should start
>> planning the next release to get these new and improved capabilities into a
>> stable version for users.
>>
>> Thanks!
>> Kevin
>>
>> On 2/14/18, 13:42, "Marc"  wrote:
>>
>> Hello Everyone,
>>   I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
>> really useful features and bug fixes in place or nearly up for review.
>> I am
>> proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
>> activities are complete.
>>
>>We've had some very useful processors added (UpdateAttribute added
>> RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
>> updates, and various bug fixes. If everyone is favorable to begin the
>> release process I am happy to act as RM if no one else is interested.
>>Thanks for your consideration,
>>Marc
>>
>>
>>
>>

Re: ASF -> GitHub sync

[Marc Parisi]

I've seen it get stuck only to unstick with another merge

On Fri, May 11, 2018, 8:50 AM Mike Thomsen  wrote:

> I approved one of Matt's PRs and merged, but it seems to be taking
> unusually long for the sync to GitHub. Is something broken?
>

Re: [VOTE] Release Apache NiFi 1.6.0 (RC3)

[Marc]

+1 binding

   -- verified sigs and hashes.
   -- confirmed a parallel build with tests
   -- started secure cluster and interfaced with Apache NiFi MiNiFi C++



On Wed, Apr 4, 2018 at 6:33 AM, Takanobu Asanuma  wrote:
> Thanks for all your efforts, Joe.
>
> +1(non-binding).
>  - Verified all hashes
>  - Succeeded "mvn -T 2.0C clean install -Prpm,generateArchives -DskipTests"
>  - Started a secure cluster with three NiFi nodes and three ZK nodes using 
> Docker (Verified the whitelist feature)
>  - Verified some dataflows work fine
>
> -Takanobu Asanuma
>
> -Original Message-
> From: Joe Witt [mailto:joew...@apache.org]
> Sent: Wednesday, April 04, 2018 8:49 AM
> To: dev@nifi.apache.org
> Subject: [VOTE] Release Apache NiFi 1.6.0 (RC3)
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi 
> nifi-1.6.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1124
>
> The Git tag is nifi-1.6.0-RC3
> The Git commit ID is f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
>
> Checksums of nifi-1.6.0-source-release.zip:
> SHA1: d1e1c24f9af809bf812982962b61d07df4f1131e
> SHA256: 1e5028d594bb402aa36460f1b826d4e8a664ad6f0538deed20286cbf3c621fb8
> SHA512: 
> 8cb10cbafa6feeed712dbc0cf076496d6bc014276aab71383ff3481d8ea719cf1f39766abc76c75ba58ffca747df3bd6d9bac82e410de1c78673dcd16a5ddfee
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 162 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12342422
>
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.6.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items 
> including checking hashes, signatures, build from source, and test.  The 
> please vote:
>
> [ ] +1 Release this package as nifi-1.6.0 [ ] +0 no opinion [ ] -1 Do not 
> release this package because...

Re: [VOTE] Release Apache NiFi 1.6.0 (RC2)

[Marc Parisi]

+1 binding

Built and tested flow on osx and centos
Worked through release helper's guide
Validates Sig's and hashes.



On Wed, Mar 28, 2018, 6:10 AM Pierre Villard 
wrote:

> +1 (binding)
>
> - went through the release helper guide
> - full clean install on OS X
> - test unsecured and secured cluster setups and communications with
> Registry and MiNiFi Java
> - various flows I have are running as expected
> - confirmed the fix that blocked the previous RC
>
> Thanks Joe for taking care of the RM duties and thanks to everyone that
> contributed in this release.
>
> Pierre
>
> 2018-03-28 11:46 GMT+02:00 Koji Kawamura :
>
> > +1 (binding)
> >
> > - Confirmed hashes
> > - Built with include-atlas profile
> > - Confirmed various flows with 3 node secured cluster on Ubuntu
> > - Tested integration with Hadoop environment and NiFi Registry
> >
> > Koji
> >
> > On Wed, Mar 28, 2018 at 12:27 PM, Andrew Lim  >
> > wrote:
> > > +1 (non-binding)
> > >
> > > -Ran full clean install on OS X (10.11.6)
> > > -Tested integration with Secure NiFi Registry (1.5.0)
> > > -Tested fine grained restricted component policies.  Verified two
> issues
> > discovered while testing RC1 have been fixed in RC2 [1, 2]
> > > -Ran basic flows successfully
> > > -Reviewed documentation
> > >
> > > Drew
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-5008
> > > [2] https://issues.apache.org/jira/browse/NIFI-5009
> > >
> > >
> > >> On Mar 26, 2018, at 11:34 PM, Joe Witt  wrote:
> > >>
> > >> Hello,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > >> NiFi nifi-1.6.0.
> > >>
> > >> The source zip, including signatures, digests, etc. can be found at:
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1123
> > >>
> > >> The Git tag is nifi-1.6.0-RC2
> > >> The Git commit ID is b5935ec81a7cbc048820781ac62cd96bbea5b232
> > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > b5935ec81a7cbc048820781ac62cd96bbea5b232
> > >>
> > >> Checksums of nifi-1.6.0-source-release.zip:
> > >> SHA1: 009f1e2e3c17e38f21f27170b9c06228d11653c0
> > >> SHA256: 39941a5b25427e2b4cc5ba8206084ff92df58863f29ddd097d4ac1e85424
> > beb9
> > >> SHA512: 1773417a48665e3cda22180ea7f401bc8190ebddbf3f7bc29831e46e7ab0
> > a07694c6e478d252fa573209d4a3c8132a522a8507b6a8784669ab7364847a07e234
> > >>
> > >> Release artifacts are signed with the following key:
> > >> https://people.apache.org/keys/committer/joewitt.asc
> > >>
> > >> KEYS file available here:
> > >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>
> > >> 146 issues were closed/resolved for this release:
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12342422
> > >>
> > >> Release note highlights can be found here:
> > >> https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.6.0
> > >>
> > >> The vote will be open for 72 hours.
> > >> Please download the release candidate and evaluate the necessary items
> > >> including checking hashes, signatures, build
> > >> from source, and test.  The please vote:
> > >>
> > >> [ ] +1 Release this package as nifi-1.6.0
> > >> [ ] +0 no opinion
> > >> [ ] -1 Do not release this package because...
> > >
> >
>

Re: trouble installing minifi

[Marc]

Hi,
  I was reminded that on the download page there is a comment
regarding the source release tarball:

  "Note: If you experience any issues with building, please try
removing Scanner.cpp, Parser.hpp, Parser.cpp, *.hh from the
extensions/expression-language folder and rebuild"

  This only applies to the current source tarball:
nifi-minifi-cpp-0.4.0-source.tar.gz

  Sorry for the inconvenience and let us know if you have additional problems.




On Thu, Mar 15, 2018 at 6:09 PM, Marc  wrote:
> Hi,
>   What is your os? Did you use the cmake instructions or bootstrap?
>
> On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com"  wrote:
>>
>> I've been following the instructions for installing minifi, and everything
>> worked up until i ran the 'make' command from the build folder. Partway
>> through the make process, I get the following errors (see below). Has anyone
>> seen this before, and what can I do to fix it?
>>
>> Thanks in advance for your help..
>>
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:
>> In member function ‘int
>> org::apache::nifi::minifi::expression::Driver::lex(org::apache::nifi::minifi::expression::Parser::semantic_type*,
>> org::apache::nifi::minifi::expression::Parser::location_type*)’:
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:582:9:
>> error: no match for ‘operator=’ (operand types are ‘std::istream {aka
>> std::basic_istream}’ and ‘std::istream* {aka
>> std::basic_istream*}’)
>> In file included from /usr/include/c++/5/iostream:40:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/istream:625:7: note: candidate:
>> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
>> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
>> char; _Traits = std::char_traits]
>>operator=(basic_istream&& __rhs)
>>^
>> /usr/include/c++/5/istream:625:7: note:   no known conversion for argument
>> 1 from ‘std::istream* {aka std::basic_istream*}’ to
>> ‘std::basic_istream&&’
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:585:10:
>> error: no match for ‘operator=’ (operand types are ‘std::ostream {aka
>> std::basic_ostream}’ and ‘std::ostream* {aka
>> std::basic_ostream*}’)
>> In file included from /usr/include/c++/5/iostream:39:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/ostream:402:7: note: candidate:
>> std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT,
>> _Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT =
>> char; _Traits = std::char_traits]
>>operator=(basic_ostream&& __rhs)
>>^
>> /usr/include/c++/5/ostream:402:7: note:   no known conversion for argument
>> 1 from ‘std::ostream* {aka std::basic_ostream*}’ to
>> ‘std::basic_ostream&&’
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:802:44:
>> error: cannot convert ‘std::istream {aka std::basic_istream}’ to
>> ‘std::istream* {aka std::basic_istream*}’ in assignment
>> In file included from /usr/include/c++/5/iostream:40:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/istream: In constructor
>> ‘yyFlexLexer::yyFlexLexer(std::istream*, std::ostream*)’:
>> /usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT,
>> _Traits>::basic_istream() [with _CharT = char; _Traits =
>> std::char_traits]’ is protected
>>basic_istream()
>>^
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:913:75:
>> error: within this context
>> In file included from /usr/include/c++/5/iostream:39:0,
>>  from
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
>> /usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT,
>> _Traits>::basic_ostream() [with _CharT = char; _Traits =
>> std::char_traits]’ is protected
>>basic_ostream()
>>^
>>
>> /Users/apiri/Development/code/apache/nifi-minifi-cpp/extensions/

Re: trouble installing minifi

[Marc]

Hi,
  What is your os? Did you use the cmake instructions or bootstrap?

On Mar 15, 2018 6:06 PM, "mjrudd...@gmail.com"  wrote:

> I've been following the instructions for installing minifi, and everything
> worked up until i ran the 'make' command from the build folder. Partway
> through the make process, I get the following errors (see below). Has
> anyone seen this before, and what can I do to fix it?
>
> Thanks in advance for your help..
>
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp: In member function ‘int
> org::apache::nifi::minifi::expression::Driver::lex(org::
> apache::nifi::minifi::expression::Parser::semantic_type*,
> org::apache::nifi::minifi::expression::Parser::location_type*)’:
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:582:9: error: no match for
> ‘operator=’ (operand types are ‘std::istream {aka
> std::basic_istream}’ and ‘std::istream* {aka
> std::basic_istream*}’)
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream:625:7: note: candidate:
> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_istream&& __rhs)
>^
> /usr/include/c++/5/istream:625:7: note:   no known conversion for
> argument 1 from ‘std::istream* {aka std::basic_istream*}’ to
> ‘std::basic_istream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:585:10: error: no match for
> ‘operator=’ (operand types are ‘std::ostream {aka
> std::basic_ostream}’ and ‘std::ostream* {aka
> std::basic_ostream*}’)
> In file included from /usr/include/c++/5/iostream:39:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/ostream:402:7: note: candidate:
> std::basic_ostream<_CharT, _Traits>& std::basic_ostream<_CharT,
> _Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_ostream&& __rhs)
>^
> /usr/include/c++/5/ostream:402:7: note:   no known conversion for
> argument 1 from ‘std::ostream* {aka std::basic_ostream*}’ to
> ‘std::basic_ostream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:802:44: error: cannot convert
> ‘std::istream {aka std::basic_istream}’ to ‘std::istream* {aka
> std::basic_istream*}’ in assignment
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream: In constructor 
> ‘yyFlexLexer::yyFlexLexer(std::istream*,
> std::ostream*)’:
> /usr/include/c++/5/istream:606:7: error: ‘std::basic_istream<_CharT,
> _Traits>::basic_istream() [with _CharT = char; _Traits =
> std::char_traits]’ is protected
>basic_istream()
>^
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:913:75: error: within this
> context
> In file included from /usr/include/c++/5/iostream:39:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/ostream:384:7: error: ‘std::basic_ostream<_CharT,
> _Traits>::basic_ostream() [with _CharT = char; _Traits =
> std::char_traits]’ is protected
>basic_ostream()
>^
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:913:75: error: within this
> context
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:915:7: error: no match for
> ‘operator=’ (operand types are ‘std::istream {aka
> std::basic_istream}’ and ‘std::istream* {aka
> std::basic_istream*}’)
> In file included from /usr/include/c++/5/iostream:40:0,
>  from /Users/apiri/Development/code/
> apache/nifi-minifi-cpp/extensions/expression-language/Scanner.cpp:96:
> /usr/include/c++/5/istream:625:7: note: candidate:
> std::basic_istream<_CharT, _Traits>& std::basic_istream<_CharT,
> _Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT =
> char; _Traits = std::char_traits]
>operator=(basic_istream&& __rhs)
>^
> /usr/include/c++/5/istream:625:7: note:   no known conversion for
> argument 1 from ‘std::istream* {aka std::basic_istream*}’ to
> ‘std::basic_istream&&’
> /Users/apiri/Development/code/apache/nifi-minifi-cpp/
> extensions/expression-language/Scanner.cpp:916:8: error: no match for
> ‘operator=’ (operand types are ‘std::ostream {aka
> std::basic_ostream}’ and ‘std::ostrea

[DISCUSS] Apache NiFi MiNiFi C++ 0.5.0

[Marc]

Hello Everyone,
  I wanted to discuss releasing 0.5.0 in the coming weeks. We have some
really useful features and bug fixes in place or nearly up for review. I am
proposing that we release Apache NiFi MiNiFi C++ 0.5.0 when these
activities are complete.

   We've had some very useful processors added (UpdateAttribute added
RouteOnAttribute coming ) , MQTT security, support for SUSE/SLES, C2
updates, and various bug fixes. If everyone is favorable to begin the
release process I am happy to act as RM if no one else is interested.
   Thanks for your consideration,
   Marc

Re: Trouble with setting up SSL connecting MiNiFi to NiFi

[Marc]

Jonah,
  Sorry for the double reply.
https://issues.apache.org/jira/browse/MINIFICPP-396 is the ticket
corresponding to that PR. It may address your issue depending no whether or
not you are currently using the Context service to configure the RPG. It
may also address another issue preventing proper setup, but the CA trust
issue is likely not addressed with the PR I sent a few minutes ago.
  Thanks,
  Marc


On Fri, Feb 9, 2018 at 5:44 PM, Marc  wrote:

> Jonah,
>
>   There is a pull request to address some of the configuration of these
> objects since there were two routes to configure it ( Context Service and
> minifi.properties ) : https://github.com/apache/nifi-minifi-cpp/pull/263
> ; however,
>   I'm not sure this is your issues since the curl_easy_perform implies
> that the peer certificate cannot be authenticated -- "Peer certificate
> cannot be authenticated with given CA certificates"
>
>   Are you setting an SSL context service? Does the CA certificate path
> contain the entire trust chain?
>
>   Thanks,
>   Marc
>
> On Fri, Feb 9, 2018 at 5:20 PM, Jonah Husson 
> wrote:
>
>> Hey All,
>>
>> Figured I'd shoot off an email before looking into issue reporting, in
>> case
>> this is a product of my own stupidity rather than an actual bug.
>>
>> I'm trying to get MiNiFi communicating with a NiFi cluster on an internal
>> network running with SSL.  I'm able to connect to NiFi from a web browser
>> after importing the correct certificates, but attempting to actually
>> transfer a file with minifi produces the following result:
>>
>> [2018-02-09 15:45:55.136] [main] [info] MiNiFi started
>> [2018-02-09 15:45:57.923] [org::apache::nifi::minifi::pr
>> ocessors::GetFile]
>> [info] GetFile process
>> /home/jonah/optimus/data/dynamic/ready_logs/testcopy2.txt
>> [2018-02-09 15:45:58.339] [org::apache::nifi::minifi::utils::HTTPClient]
>> [debug] Setting callback for
>> [2018-02-09 15:45:58.401] [org::apache::nifi::minifi::co
>> re::ProcessSession]
>> [info] Transferring 3b086abc-0dda-11e8-ab09-c85b769e9522 from GetFile to
>> relationship success
>> [2018-02-09 15:45:58.438]
>> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [debug] Refreshing
>> the peer list since there are none configured.
>> [2018-02-09 15:45:58.439] [org::apache::nifi::minifi::utils::HTTPClient]
>> [debug] https://rs0.internal.optimusride.com:9093/nifi-api/site-to-site
>> is
>> a secure url
>> [2018-02-09 15:45:58.439] [org::apache::nifi::minifi::utils::HTTPClient]
>> [debug] Submitting to
>> https://rs0.internal.optimusride.com:9093/nifi-api/site-to-site
>> [2018-02-09 15:45:58.553] [org::apache::nifi::minifi::utils::HTTPClient]
>> [error] curl_easy_perform() failed Peer certificate cannot be
>> authenticated
>> with given CA certificates
>>
>> [2018-02-09 15:45:58.553]
>> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [error]
>> ProcessGroup::refreshRemoteSite2SiteInfo -- curl_easy_perform() failed
>>
>> [2018-02-09 15:45:58.553]
>> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [debug] Obtained
>> protocol from available_protocols_
>> [2018-02-09 15:45:58.553]
>> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [info] no protocol,
>> yielding
>> [2018-02-09 15:46:01.541] [org::apache::nifi::minifi::utils::HTTPClient]
>> [debug] Setting callback for
>> [2018-02-09 15:46:02.701] [org::apache::nifi::minifi::FlowController]
>> [info] Stop Flow Controller
>> [2018-02-09 15:46:04.748] [org::apache::nifi::minifi::utils::HTTPClient]
>> [debug] Setting callback for
>> [2018-02-09 15:46:05.137] [org::apache::nifi::minifi::FlowController]
>> [info] Unload Flow Controller
>> [2018-02-09 15:46:05.137] [main] [info] MiNiFi exit
>>
>> I'm not entirely sure what I'm doing wrong here, I'm fairly sure my
>> certificate setup is fine.  NiFi's keystore has a cert/private key signed
>> by a CA i self-signed and created locally, it's truststore has the public
>> key that corresponds to the client certificate and private key on MiNiFi,
>> and MiNiFi has the certificate used to sign the one in NiFi's keystore.
>>
>> The best guess I have stems from the fact that the log message  is a
>> secure url occurs, but the message that configure_secure_connection(CURL
>> *http_session) should play if it runs doesn't come up, which leads me to
>> beleive that ssl_context_service_ isn't initialized properly for some
>> reason (see line 129 in /extensions/http-curl/HTTPClient.cpp, only place
>> I
>> see either of those methods called).
>>
>> Let me know if you have any insight on this, frankly I haven't found much
>> documentation on the SSL setup for MiNiFi at all, so it's totally possible
>> I did something horribly wrong there.  I'd also be happy to make a bug
>> report if y'all think this warrants one.
>>
>> Best,
>> Jonah.
>>
>
>

Re: Trouble with setting up SSL connecting MiNiFi to NiFi

[Marc]

Jonah,

  There is a pull request to address some of the configuration of these
objects since there were two routes to configure it ( Context Service and
minifi.properties ) : https://github.com/apache/nifi-minifi-cpp/pull/263 ;
however,
  I'm not sure this is your issues since the curl_easy_perform implies that
the peer certificate cannot be authenticated -- "Peer certificate cannot be
authenticated with given CA certificates"

  Are you setting an SSL context service? Does the CA certificate path
contain the entire trust chain?

  Thanks,
  Marc

On Fri, Feb 9, 2018 at 5:20 PM, Jonah Husson  wrote:

> Hey All,
>
> Figured I'd shoot off an email before looking into issue reporting, in case
> this is a product of my own stupidity rather than an actual bug.
>
> I'm trying to get MiNiFi communicating with a NiFi cluster on an internal
> network running with SSL.  I'm able to connect to NiFi from a web browser
> after importing the correct certificates, but attempting to actually
> transfer a file with minifi produces the following result:
>
> [2018-02-09 15:45:55.136] [main] [info] MiNiFi started
> [2018-02-09 15:45:57.923] [org::apache::nifi::minifi::processors::GetFile]
> [info] GetFile process
> /home/jonah/optimus/data/dynamic/ready_logs/testcopy2.txt
> [2018-02-09 15:45:58.339] [org::apache::nifi::minifi::utils::HTTPClient]
> [debug] Setting callback for
> [2018-02-09 15:45:58.401] [org::apache::nifi::minifi::
> core::ProcessSession]
> [info] Transferring 3b086abc-0dda-11e8-ab09-c85b769e9522 from GetFile to
> relationship success
> [2018-02-09 15:45:58.438]
> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [debug] Refreshing
> the peer list since there are none configured.
> [2018-02-09 15:45:58.439] [org::apache::nifi::minifi::utils::HTTPClient]
> [debug] https://rs0.internal.optimusride.com:9093/nifi-api/site-to-site is
> a secure url
> [2018-02-09 15:45:58.439] [org::apache::nifi::minifi::utils::HTTPClient]
> [debug] Submitting to
> https://rs0.internal.optimusride.com:9093/nifi-api/site-to-site
> [2018-02-09 15:45:58.553] [org::apache::nifi::minifi::utils::HTTPClient]
> [error] curl_easy_perform() failed Peer certificate cannot be authenticated
> with given CA certificates
>
> [2018-02-09 15:45:58.553]
> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [error]
> ProcessGroup::refreshRemoteSite2SiteInfo -- curl_easy_perform() failed
>
> [2018-02-09 15:45:58.553]
> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [debug] Obtained
> protocol from available_protocols_
> [2018-02-09 15:45:58.553]
> [org::apache::nifi::minifi::RemoteProcessorGroupPort] [info] no protocol,
> yielding
> [2018-02-09 15:46:01.541] [org::apache::nifi::minifi::utils::HTTPClient]
> [debug] Setting callback for
> [2018-02-09 15:46:02.701] [org::apache::nifi::minifi::FlowController]
> [info] Stop Flow Controller
> [2018-02-09 15:46:04.748] [org::apache::nifi::minifi::utils::HTTPClient]
> [debug] Setting callback for
> [2018-02-09 15:46:05.137] [org::apache::nifi::minifi::FlowController]
> [info] Unload Flow Controller
> [2018-02-09 15:46:05.137] [main] [info] MiNiFi exit
>
> I'm not entirely sure what I'm doing wrong here, I'm fairly sure my
> certificate setup is fine.  NiFi's keystore has a cert/private key signed
> by a CA i self-signed and created locally, it's truststore has the public
> key that corresponds to the client certificate and private key on MiNiFi,
> and MiNiFi has the certificate used to sign the one in NiFi's keystore.
>
> The best guess I have stems from the fact that the log message  is a
> secure url occurs, but the message that configure_secure_connection(CURL
> *http_session) should play if it runs doesn't come up, which leads me to
> beleive that ssl_context_service_ isn't initialized properly for some
> reason (see line 129 in /extensions/http-curl/HTTPClient.cpp, only place I
> see either of those methods called).
>
> Let me know if you have any insight on this, frankly I haven't found much
> documentation on the SSL setup for MiNiFi at all, so it's totally possible
> I did something horribly wrong there.  I'd also be happy to make a bug
> report if y'all think this warrants one.
>
> Best,
> Jonah.
>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.4.0 RC1

[Marc Parisi]

 +1 ( binding ) to release

 * Verified signatures and hashes as well, built using the helper's
guide for U16.

 * Built on U16 32 bit last night and CENTOS earlier today using the
bootstrap process on the git commit ID to enable all features for those
platforms. I ran bootstrap.sh -e -n -b on each; Ran flows on each to
connect to my host machine ( OSX ), using Site to Site for validation.

 * Verified common processors, PCAP, EL, ES.

 * Build successfully moments ago from the source tar on OSX ( did not
attempt on CENTOS 7 as Andy did ) -- I think we can simply make note of
this. Also ran this locally

 * verified functionality of minificontroller to get stats from the
running minifi instance. Verified from the readme's discussion of it.

 * L&N look good.

 Thanks!

On Thu, Jan 25, 2018 at 11:55 AM, Tony Kurc  wrote:

> +1 (binding)
>
> Verified signatures and hashes. Built using helper guide on in an Ubuntu
> 16.04 (x86_64) docker container. Did not try the bootstrap script (it
> failed when my container didn't have a working sudo, figured this was a
> non-issue for most use cases and moved on) . Ran a couple very simple
> flows. One thing I didn't do was run through all the options for
> building... I believe I did a fairly base build. Reviewed the LICENSE and
> NOTICE.
>
>
>
> On Thu, Jan 25, 2018 at 10:51 AM, Joe Witt  wrote:
>
> > +1 (binding)
> >
> > Full build/testing done on osx.  All sigs/hashes checkout.  L&N on
> > source and binary artifacts solid.  Ran some tests flows grabbing data
> > and sending to nifi via s2s based on flows created using template
> > converter in minifi toolkit.
> >
> > Nice progress in here!!!  Thanks
> >
> > On Wed, Jan 24, 2018 at 1:36 AM, Aldrin Piri  wrote:
> > > Hello Apache NiFi Community,
> > >
> > > I am pleased to call this vote for the source release of Apache NiFi
> > MiNiFi
> > > C++, nifi-minifi-cpp-0.4.0.
> > >
> > > The source archive, signature, and digests can be located at:
> > >
> > > Source Archive:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz
> > >
> > > GPG armored signature:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.asc
> > >
> > > Source MD5:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.md5
> > >
> > > Source SHA1:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.sha1
> > >
> > > Source SHA256:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.sha256
> > >
> > > The Git tag is minifi-cpp-0.4.0-RC1
> > > The Git commit hash is c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> > > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.
> > git;a=commit;h=c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> > > * https://github.com/apache/nifi-minifi-cpp/commit/
> > c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> > >
> > > Checksums of nifi-minifi-cpp-0.4.0-source.tar.gz:
> > > MD5: 27d82a635cee3f97841eb6af01248712
> > > SHA1: 3b8bb029bcca64897223f7fb27122ac9642cd92b
> > > SHA256: 887879d65514ccc7ee598ba650d05f7ff56145d8462707d38b137363ea97
> 1965
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/aldrin
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> > >
> > > 49 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12321520&version=12341641
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/MINIFI/
> > Release+Notes#ReleaseNotes-Versioncpp-0.4.0
> > >
> > > The vote will close 27 January at 12PM EST [1].
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> Then
> > > please vote:
> > >
> > > [ ] +1 Release this package as nifi-minifi-cpp-0.4.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > >
> > >
> > > [1] You can determine this time for your local time zone at
> > > https://s.apache.org/minifi-cpp-0.4.0-rc1-close
> >
>

Re: [VOTE] Release Apache NiFi MiNiFi 0.4.0 RC2

[Marc Parisi]

+1 binding to release this package as minifi-0.4.0

  * Verified sigs/hashes
  * Built and ran with typical test flows across builds ( to include
SiteToSite )

  Looks good thanks!

On Fri, Jan 19, 2018 at 3:28 PM, Bryan Bende  wrote:

> +1 binding
>
> Ran through everything in the release helper and looked good, thanks!
>
> On Fri, Jan 19, 2018 at 3:03 PM, Matt Gilman 
> wrote:
> > +1 Release this package as minifi-0.4.0
> >
> > Verified hashes, signature, build, etc. Ran sample flows and everything
> > looks good.
> >
> > Thanks for RMing Aldrin!
> >
> > Matt
> >
> > On Fri, Jan 19, 2018 at 3:24 AM, Koji Kawamura 
> > wrote:
> >
> >> Verified the hash, built on Windows Server 2016, Java 1.8.0_144
> >> successfully.
> >> Confirmed that the basic template transform capability with NiFi 1.5.0
> >> including RemoteProcessGroup.
> >> The getting-started example flow, tailing a file at MiNiFi (0.4.0 RC2)
> >> and sending it via S2S to NiFi (1.5.0) worked as expected.
> >> https://nifi.apache.org/minifi/getting-started.html
> >> Confirmed that the config.yml created by the toolkit has the correct
> >> ID for the input port.
> >>
> >> +1 (binding) Release this package as minifi-0.4.0
> >>
> >> On Fri, Jan 19, 2018 at 5:55 AM, Aldrin Piri  wrote:
> >> > Hello,
> >> >
> >> > I am pleased to call this vote for the source release of Apache NiFi
> >> MiNiFi nifi-minifi-0.4.0.
> >> >
> >> > The source zip, including signatures, digests, etc. can be found at:
> >> > https://repository.apache.org/content/repositories/orgapachenifi-1119
> >> >
> >> > The Git tag is nifi-minifi-0.4.0-RC2
> >> > The Git commit ID is 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> >> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=
> >> 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> >> > https://github.com/apache/nifi-minifi/commit/
> >> 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> >> >
> >> > Checksums of nifi-minifi-0.4.0-source-release.zip:
> >> > MD5: 237bb2f3fe26ff6451273c3c39579bf6
> >> > SHA1: 2d53dd08b55a2799da97008bf971657546c0a752
> >> > SHA256: b0ee425f7c214d423f22b75aa2006dcdabf407cd29b0bd2c4f8a8ea3a3ec
> 4b18
> >> >
> >> > Release artifacts are signed with the following key:
> >> > https://people.apache.org/keys/committer/aldrin.asc
> >> >
> >> > KEYS file available here:
> >> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >> >
> >> > 5 issues were closed/resolved for this release:
> >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >> projectId=12319921&version=12342439
> >> >
> >> > Release note highlights can be found here:
> >> > https://cwiki.apache.org/confluence/display/MINIFI/
> >> Release+Notes#ReleaseNotes-Version0.4.0
> >> >
> >> > The vote will be open until 4:00PM EST, 22 January 2018 [1].
> >> >
> >> > Please download the release candidate and evaluate the necessary items
> >> including checking hashes, signatures, build
> >> > from source, and test.  Then please vote:
> >> >
> >> > [ ] +1 Release this package as minifi-0.4.0
> >> > [ ] +0 no opinion
> >> > [ ] -1 Do not release this package because...
> >> >
> >> > Thanks!
> >> >
> >> > [1] You can determine this time for your local time zone at
> >> https://s.apache.org/minifi-0.4.0-rc2-close
> >>
>

Re: [VOTE] Release Apache NiFi 1.5.0 (RC1)

[Marc]

+1, binding.

   * Verified sigs/hashes
   * Used release guide with no issues
   * Ran through some tests with flow versioning functionality.
   * Ran usual test flows



On Wed, Jan 10, 2018 at 6:38 AM, Marco Gaido  wrote:

> +1 (not binding). Ran through release guide with no issues and run some
> workflows.
>
> 2018-01-10 4:41 GMT+01:00 Jeremy Dyer :
>
> > +1 non binding. Ran through release guide with no issues and ran several
> > test workflows from personal projects
> >
> > - Jeremy Dyer
> >
> > > On Jan 9, 2018, at 8:11 PM, Andy LoPresto 
> wrote:
> > >
> > > +1, binding
> > >
> > > I performed the following verifications:
> > >
> > > * verified the GPG key signature
> > > * verified the MD5/SHA1/SHA256 checksums
> > > * verified the git commit ID
> > > * verified the presence of LICENSE, NOTICE, and README
> > > * verified the Maven build was successful, including all unit tests,
> RAT
> > check, and code style guidelines
> > > * verified the application started successfully
> > > * verified the new behavior for host header handling was present
> > > * verified the application integrates successfully with the Apache NiFi
> > Registry
> > > * verified the CountText processor works as anticipated
> > > * verified the flow versioning functionality by making local changes,
> > committing, and restoring prior versions of the flow
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > >> On Jan 9, 2018, at 9:13 AM, Mark Payne  wrote:
> > >>
> > >> +1 (binding) - Release this package as nifi-1.5.0
> > >>
> > >> Was able to successfully build with contrib-check and grpc profile.
> > Verified MD5 sum.
> > >> Started up, added a Flow Registry Client pointing to an existing Flow
> > Registry and was
> > >> able to immediately import a flow and start it running. This flow also
> > verified the fix for
> > >> NIFI-4749 made it into the build yesterday.
> > >>
> > >> Thanks for taking on the RM duties this time, Joe! And a big thank you
> > and congrats
> > >> to all of the members of the community that contributed to this
> release
> > - code, JIRA's,
> > >> docs, and support!
> > >>
> > >> Thanks
> > >> -Mark
> > >>
> > >>
> > >>> On Jan 9, 2018, at 5:19 AM, Joe Witt  wrote:
> > >>>
> > >>> Hello,
> > >>>
> > >>> I am pleased to be calling this vote for the source release of Apache
> > >>> NiFi nifi-1.5.0.
> > >>>
> > >>> The source zip, including signatures, digests, etc. can be found at:
> > >>> https://repository.apache.org/content/repositories/
> orgapachenifi-1116
> > >>>
> > >>> The Git tag is nifi-1.5.0-RC1
> > >>> The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >>> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >>>
> > >>> Checksums of nifi-1.5.0-source-release.zip:
> > >>> MD5: 046f2dde4af592dd8c05e55c2bbb3c4f
> > >>> SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c
> > >>> SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94
> > 2d13
> > >>>
> > >>> Release artifacts are signed with the following key:
> > >>> https://people.apache.org/keys/committer/joewitt.asc
> > >>>
> > >>> KEYS file available here:
> > >>> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >>>
> > >>> 195 issues were closed/resolved for this release:
> > >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12341668
> > >>>
> > >>> Release note highlights can be found here:
> > >>> https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.5.0
> > >>>
> > >>> The vote will be open for 72 hours.
> > >>> Please download the release candidate and evaluate the necessary
> items
> > >>> including checking hashes, signatures, build
> > >>> from source, and test.  The please vote:
> > >>>
> > >>> [ ] +1 Release this package as nifi-1.5.0
> > >>> [ ] +0 no opinion
> > >>> [ ] -1 Do not release this package because...
> > >>
> > >
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Kevin Doran

[Marc]

Congrats Kevin! Agreed, well deserved!

On Jan 3, 2018 9:48 AM, "Scott Aslan"  wrote:

Congrats Kevin! Well deserved!

On Wed, Jan 3, 2018 at 9:45 AM, Matt Burgess  wrote:

> Congrats and welcome aboard Kevin!
>
> On Wed, Jan 3, 2018 at 9:17 AM, Bryan Bende  wrote:
> > On behalf of the Apache NiFi PMC, I am very pleased to announce that
> > Kevin Doran has accepted the PMC's invitation to become a committer on
> > the Apache NiFi project. We greatly appreciate all of Kevin's hard
> > work and generous contributions to the project. We look forward to his
> > continued involvement in the project.
> >
> > Kevin has made significant contributions to the NiFi Registry project,
> > especially around setting up the security model & REST APIs, and was a
> > major contributor to getting the first release out. You also may have
> > interacted with him on the mailing lists already, as he is always
> > willing to dig into questions/issues and help out.
> >
> > Welcome and congratulations!
>

Re: [VOTE] Release Apache NiFi Registry 0.1.0

[Marc]

+1 binding  to release this package as nifi-registry-0.1.0

  verified sigs, commits, readme.

  Ran some basic tests, including validating creating groups, committing
versions, verifying that there was a way to identify that uncommitted
changes existed.

  Ensured that my bucket's flow's change log matched what I actually did in
the NiFi PR.

  Comments:

Really enjoyed testing this. In my console I saw a 409 ( which I think
Chrome incorrectly identified from the 405 being returned on
http://localhost:18080/nifi-registry-api/access/token/kerberos )

The only option defined for Kerberos was the expiration. I thought
about creating a minor ticket as I didn't see one in JIRA,  but I assume
that was intended.

After creating my bucket through settings an encountered
https://issues.apache.org/jira/browse/NIFIREG-88 .

The issue is likely client side ( hence why I made a minor ticket ) as
I can switch tabs to show settings; however, until I realized this I waited
nearly 2 minutes for settings to show.

I'm willing to chalk this up to user error or my environment.

    Best Regards,
Marc

On Thu, Dec 28, 2017 at 3:35 PM, Joe Witt  wrote:

> +1 (binding) Release this package as nifi-registry-0.1.0
>
> Release verification process
> -pull source artifacts
> -verify sigs
> -verify commit id
> -verify commit history reflects latest changes (based off commit
> id/history)
> -verify source README
> -verify source L&N and that it is consistent with the work done in
>https://issues.apache.org/jira/browse/NIFIREG-66
> -verify build w/contrib check
> -verify binary/assembly README
> -verify binary/assembly L&N and that it is consistent with work done in
>https://issues.apache.org/jira/browse/NIFIREG-66
> -test registry on its own (manual/user testing)
> -review registry docs
> -setup certificate based secure reg setup/test
> - build nifi with registry integration PR
> - verify interaction with secure (certs based) nifi/secure registry
>
> Tests
> - create empty group
> - make local changes / view diffs / go to
> - make sure nifi cannot do anything with the registry when its cert
> lacks proxy auth
> - once proxy auth added all options available
> - verify can publish new versions/comments/ensure input is escaped
> - change versions on a live flow with and without enqueued data
>
> Observations
> - Having a default URL handler to show the 'you may have mistyped'
> type page from nifi would be nice
> - We should improve the logic of when components are started/stopped
> to make version changes.  For position changes only components should
> not start/stop
> - There are a lot of very cool features to add from here but this is a
> pretty awesome first version with a range of excellent security
> options/polish.
>
>
> This is going to be a huge step forward for the community!
>
> Thanks
> Joe
>
> On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende  wrote:
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry 0.1.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> >
> > The Git tag is nifi-registry-0.1.0-RC1
> > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=
> 81b99e7b04491eabb72ddf30754053ca12d0fcca
> >
> > Checksums of nifi-registry-0.1.0-source-release.zip:
> > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 65 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12320920&version=12340217
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> >
> > The vote will be open for 96 hours.
> >
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> >
> > The please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.1.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

Re: [VOTE] Release Apache NiFi MiNiFi 0.3.0 - RC3

[Marc]

+1 -- binding to release minifi-0.3.0

verified hashes and sigs
successful build w/ contrib-check
ran some MiNiFi -> NiFi flows I use for testing.

Looks great!

On Tue, Dec 19, 2017 at 8:59 AM, Pierre Villard  wrote:

> +1 - binding - release this package as minifi-0.3.0
>
> Went through the release helper guide. Executed some workflows MiNiFi ->
> NiFi. All good.
>
> Thanks to everyone involved in this release!
>
>
> 2017-12-19 14:47 GMT+01:00 Jeff Zemerick :
>
> > +1 non-binding
> >
> > verified hashes
> > verified signature
> > verified git commit
> > verified RC branch commit
> > successful build with contrib-check
> > verified the three sets of README, LICENSE, NOTICE files
> > verified windows service operation
> >
> > Thanks for putting these RCs together!
> >
> > Jeff
> >
> >
> > On Tue, Dec 19, 2017 at 12:51 AM, Koji Kawamura 
> > wrote:
> >
> > > Thanks Aldrin for updating RC again, and to all devs who contributed
> > > to MiNiFi 0.3.0 release!
> > >
> > > I confirmed:
> > > - Hashes are correct
> > > - MiNiFi Windows Service works
> > > - MiNiFi Toolset works, NiFi template -> MiNiFi config yml
> > > - NiFi template -> C2 server -> MiNiFi PullHttpChangeIngestor works
> > nicely
> > >
> > > +1 Release this package as minifi-0.3.0
> > >
> > > Koji
> > >
> > > On Tue, Dec 19, 2017 at 7:09 AM, Aldrin Piri 
> wrote:
> > > > Hello,
> > > >
> > > > I am pleased to call this vote for the source release of Apache NiFi
> > > MiNiFi,
> > > > minifi-0.3.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1114/
> > > >
> > > > The Git tag is minifi-0.3.0-RC3
> > > > The Git commit ID is f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> > > > *
> > > > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=
> commit;h=
> > > f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> > > > *
> > > > https://github.com/apache/nifi-minifi/commit/
> > > f06a7190ac07dbf02e5b0f9ee2859dea08acf3b0
> > > >
> > > > Checksums of minifi-0.3.0-source-release.zip:
> > > > MD5: 685e890486dbde4fd75db86128adf140
> > > > SHA1: 9dcf7d1b440b1247ca0c55e2ffdc75574467fed6
> > > > SHA256: a1c9be5ca4824fe98620d7df68469c8b9ea9461fb8dbecd1bdd6596e0b5d
> > ea89
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/aldrin.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 23 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12319921&version=12340598
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/MINIFI/
> > > Release+Notes#ReleaseNotes-Version0.3.0
> > > >
> > > > The vote will be open until 7:00PM EST, 21 December 2017 [1].
> > > >
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build
> > > > from source, and test.  Then please vote:
> > > >
> > > > [ ] +1 Release this package as minifi-0.3.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > > >
> > > > [1] You can determine this time for your local time zone at
> > > > https://s.apache.org/minifi-0.3.0-rc3-close
> > >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Marc Parisi

[Marc Parisi]

Thanks everyone!


Let the record state that I have been known to lift tens of hot wheels cars
at once.

On Dec 15, 2017 9:42 AM, "Yolanda Davis"  wrote:

> Congratulations Marc!
>
> On Fri, Dec 15, 2017 at 6:52 AM, Rob Moran  wrote:
>
> > Congratulations, Marc!
> >
> > On Fri, Dec 15, 2017 at 4:31 AM Pierre Villard <
> > pierre.villard...@gmail.com>
> > wrote:
> >
> > > Congrats Marc!!
> > >
> > > 2017-12-15 6:38 GMT+01:00 Jeff :
> > >
> > > > Congrats, Marc!  Treat yourself to some Kobe beef. :)
> > > >
> > > > On Thu, Dec 14, 2017 at 9:47 PM Mike Hogue 
> wrote:
> > > >
> > > > > Congrats, Marc! Well deserved!
> > > > > On Thu, Dec 14, 2017 at 20:41 Jeremy Dyer 
> wrote:
> > > > >
> > > > > > Congrats Marc! Lots of good work I have seen from you and
> > appreciate
> > > > all
> > > > > > you have given the community!
> > > > > >
> > > > > > - Jeremy Dyer
> > > > > >
> > > > > > > On Dec 14, 2017, at 8:29 PM, Scott Aslan <
> scottyas...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > Congrats!
> > > > > > >
> > > > > > >> On Thu, Dec 14, 2017 at 6:50 PM, Matt Burgess <
> > > mattyb...@apache.org
> > > > >
> > > > > > wrote:
> > > > > > >>
> > > > > > >> Congratulations Marc with a C :) Welcome aboard, looking
> forward
> > > to
> > > > > > >> more kick-arse contributions!
> > > > > > >>
> > > > > > >>> On Thu, Dec 14, 2017 at 6:47 PM, Tony Kurc  >
> > > > wrote:
> > > > > > >>> NiFi community,
> > > > > > >>> On behalf of the Apache NiFi PMC, I am pleased to announce
> that
> > > > Marc
> > > > > > >> Parisi
> > > > > > >>> has accepted the PMC's invitation to join the Apache NiFi
> PMC.
> > > We
> > > > > > >> greatly
> > > > > > >>> appreciate all of Marc's hard work and generous contributions
> > to
> > > > the
> > > > > > >>> project. We look forward to continued involvement in the
> > project.
> > > > > > >>>
> > > > > > >>> Marc is a major contributor to MiNiFi CPP; in addition to his
> > > code
> > > > > and
> > > > > > >>> review contributions, he recently release managed the 0.3.0
> > > > release.
> > > > > > He's
> > > > > > >>> super friendly, active across the NiFi project, and can lift
> a
> > > > small
> > > > > > car.
> > > > > > >>>
> > > > > > >>> Congratulations and welcome, Marc!
> > > > > > >>>
> > > > > > >>> Tony
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> > --
> > Rob
> >
>
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>

Re: [ANNOUNCE] New NiFi PMC member Jeff Storck

[Marc Parisi]

Congrats Jeffrey​!

On Dec 5, 2017 11:51 AM, "Joe Witt"  wrote:

Congrats Jeff!  You've done a lot of great and difficult work
including wading into the scary world of Kerberos!

On Tue, Dec 5, 2017 at 11:49 AM, Tony Kurc  wrote:
> NiFi community,
> On behalf of the Apache NiFi PMC, I am pleased to announce that Jeff
Storck
> has accepted the PMC's invitation to join the Apache NiFi PMC.  We greatly
> appreciate all of Jeff's hard work and generous contributions to the
> project. We look forward to continued involvement in the project.
>
> For those of you enjoying NiFi 1.4.0 release, Jeff was the release
manager,
> which is a huge complicated set of work. He's also been a long time
> contributor, committer, and a strong member of the community.
>
> Congratulations and welcome, Jeff!
>
> Tony

Re: [ANNOUNCE] New NiFi PMC member Scott Aslan

[Marc]

Congrats Scott!

On Dec 2, 2017 8:14 PM, "Kevin Doran"  wrote:

> Congrats, Scott! Keep crushing it!
>
> Get Outlook for iOS
> 
> From: Joe Witt 
> Sent: Saturday, December 2, 2017 7:27:35 PM
> To: dev@nifi.apache.org
> Subject: Re: [ANNOUNCE] New NiFi PMC member Scott Aslan
>
> congrats scott and thanks for all the awesome ui and community work youve
> done!
>
> On Dec 2, 2017 2:48 PM, "Matt Burgess"  wrote:
>
> > Congratulations Scotty! Glad to have you aboard!
> >
> >
> > > On Dec 2, 2017, at 2:46 PM, Tony Kurc  wrote:
> > >
> > > NiFi community,
> > > On behalf of the Apache NiFi PMC, I am pleased to announce that Scott
> > Aslan
> > > has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> > greatly
> > > appreciate all of Scotts's hard work and generous contributions to the
> > > project. We look forward to continued involvement in the project.
> > >
> > > Scott has been delivering as a strong committer for quite a long time,
> is
> > > making huge progress on nifi-registry, and has had wide reach to the
> > > community in many ways, to include our mailing lists.
> > >
> > > Congratulations and welcome, Scott!
> > >
> > > Tony
> >
>

[ANNOUNCE] Apache NiFi MiNiFi C++ 0.3.0 release.

[Marc]

Hello!

The Apache NiFi team would like to announce the release of Apache NiFi -
MiNiFi C++ 0.3.0.

MiNiFi is a subproject of Apache NiFi. Apache NiFi supports powerful and
scalable directed graphs of data routing, transformation, and system
mediation logic . MiNiFi provides a complementary data collection approach that
supplements the core tenets of NiFi in dataflow management, focusing on the
collection of data at the source of its creation.

MiNFI was developed with the following goals:

   - Small size and low resource consumption
   - Central management of agents
   - Generation of data provenance (full chain of custody of information)
   - Integration with NiFi for follow-on dataflow management


This MiNiFi C++ release delivers several new processors and features.
Please visit our release notes, below, for more information on these
exciting changes.

More details on Apache NiFi MiNiFi can be found here:
https://nifi.apache.org/minifi

The release artifacts can be downloaded from here:
https://nifi.apache.org/minifi/download.html

Issues closed/resolved for this list can be found here:
*https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520&version=12341640
*

Release note highlights can be found here:
*https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.3.0
*

Thank you!
The Apache NiFi team

[RESULT][VOTE] Release Apache NiFi MiNiFi C++ 0.3.0

[Marc]

Apache NiFi Community,

I am pleased to announce that the 0.3.0 release of Apache NiFi MiNiFi C++
passes with

  3 +1 (binding) votes
  3 +1 (non-binding) votes
  0 -1 votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread: https://s.apache.org/
minifi-cpp-0.3.0-rc2-result

Re: Apache MiNiFi C++ 0.3.0 Release Helper Guide

[Marc]

Hello,

I wanted to provide some clarification since I've received questions.

The following command is to create the make files via CMAKE. You do not
need PORTABLE=ON unless you are specifically building binaries that need to
be portable amongst a platform.
Instead of using the following command:

cmake -DPORTABLE=ON -DFAIL_ON_WARNINGS= ..

Use the following, unless you need your binaries to be built without
optimizations.  For the purposes of release verification PORTABLE is not
necessary, but can be useful for testing amongst machines with different
architectures.

Note that we are disabling FAIL_ON_WARNINGS for the current release , so
there is nothing after the equals operator. I've received questions about
this and it is not a typo.

cmake  -DFAIL_ON_WARNINGS= ..

   Thanks
   Marc

On Nov 27, 2017 12:00 PM, "Marc"  wrote:

> Hello Apache NiFi community,
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
> # Download latest KEYS file:
> https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> # Import keys file:
> gpg --import KEYS
>
> # Pull down nifi-minifi-cpp-0.3.0 source release artifacts for review:
>
> wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz
> wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.asc
> wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.md5
> wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.sha1
> wget https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> 0.3.0/nifi-minifi-cpp-0.3.0-source.tar.gz.sha256
>
> # Verify the signature
> gpg --verify nifi-minifi-cpp-0.3.0-source.tar.gz.asc
>
> # Verify the hashes (md5, sha1, sha256) match the source and what was
> provided in the vote email thread
> md5sum nifi-minifi-cpp-0.3.0-source.tar.gz
> sha1sum nifi-minifi-cpp-0.3.0-source.tar.gz
> sha256sum nifi-minifi-cpp-0.3.0-source.tar.gz
>
> # Untar nifi-minifi-cpp-0.3.0-source.tar.gz
> tar xf nifi-minifi-cpp-0.3.0-source.tar.gz
>
> # Verify the build works
>
> Be mindful of the pre-requisites required for the C++ version of MiNiFi,
> enumerated in the README [1] and the switching to the CMake build system
> These can vary from system to system and distribution, an example of the
> package listing for a recent Ubuntu release is:
>   cmake gcc g++ libcurl4-openssl-dev uuid-dev uuid libboost-all-dev
> libssl-dev doxygen libpython3-dev libbz2-dev liblzma-dev
>
> Once the required environment is established, a build with testing and
> linting can be performed via:
>
>   cd nifi-minifi-cpp-0.3.0-source
>   mkdir build
>   cd build
>   cmake DPORTABLE=ON -DFAIL_ON_WARNINGS= ..
>   make package
>   make test
>   make linter
>
> # Verify the contents contain a good README, NOTICE, and LICENSE.
>
> # Verify the git commit ID is correct
>
> # Verify the RC was branched off the correct git commit ID
>
> # Look at the resulting convenience assembly 
> (nifi-minifi-cpp-0.3.0-bin.tar.gz)
> found in your build directory
>
> # Make sure the README, NOTICE, and LICENSE are present and correct
>
> # Run the resulting convenience binary and make sure it works as expected
>
> Be mindful of caveats for this initial release, listed in the README.
> Since the convenience binaries include
> the scripting extension [2], Python support is needed per our README [1]
>
> For some additional assistance, a package with configuration files for
> both a MiNiFI instance and a NiFi instance available at
> https://cwiki.apache.org/confluence/display/MINIFI/Releasing
> +MiNiFi#ReleasingMiNiFi-SampleNiFiandMiNiFiConfigurationtotr
> ansmitdatafromMiNiFitoNiFiviaSitetoSite
> The provided sample configuration bundle assumes that NiFi is configured
> to listen on port 8081 and has 10001 configured for Site to Site's
> nifi.remote.input.socket.port.
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
> Thank you for your time and effort to validate the release!
>
> [1] https://github.com/apache/nifi-minifi-cpp/blob/MINIFICPP-304
> -RC2-0.3.0/README.md#system-requirements
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pa
> geId=74685143
>