Re: MiNiFi Java -> NiFi

[Aldrin Piri]

Awesome work, Matt!

In terms of project management, is there any merit in maintaining the
MINIFI tracker after the merge is complete versus using components?
Do you envision subtree releases off the nifi repo for minifi specifically?

On Wed, Apr 28, 2021 at 11:17 AM Steven Matison 
wrote:

> Way to GO!!!  This is awesome stuff.
>
>
> Steven Matison | Data Architect
> Mobile 321.848.4926
> steven.mati...@datastax.com | datastax.com
>
> > On Apr 28, 2021, at 2:08 PM, Matt Burgess  wrote:
> >
> > All,
> >
> > Now that [1] is merged, MiNiFi Java is now officially in the NiFi
> > codebase! Thanks to all who participated in discussions, reviews, and
> > testing. Here are some notes on what this means going forward:
> >
> > - All future releases of MiNiFi Java will be in lockstep with NiFi,
> > the next release version will be 1.14.0 rather than 0.6.0. MiNiFi Java
> > artifacts will be built and published as part of the NiFi release
> > process. This will allow MiNiFi to immediately benefit from
> > improvements/fixes in NiFi components instead of occasionally updating
> > the NiFi dependency version in MiNiFi Java.
> >
> > - Although we will continue to track issues in Jira under the MINIFI
> > project, PRs should be submitted against the nifi repo's main branch.
> > If you have an open PR against the nifi-minifi repo, you can port it
> > to the nifi repo by adding ".patch" to the URL of your PR, downloading
> > the patch, and applying it to a branch in your fork of the nifi repo,
> > for example:
> >
> > git checkout -b MINIFI-541
> > git apply --directory='minifi' ~/195.patch
> >
> > Sooner than later we'll make the nifi-minifi repo read-only so no more
> > PRs can be submitted against it, and we can update NiFi's PR template
> > to refer to MINIFI Jira cases as well.
> >
> > There's still work to be done of course, contributions and PR reviews
> > are most welcome!
> >
> > Regards,
> > Matt
> >
> > [1] https://github.com/apache/nifi/pull/4933
>
>

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

[Aldrin Piri]

+1, binding

comments:
* verified hashes and signature
* verified build and tests on Debian 10 and macOS 10.15
* No strong issues with L&N noticed
 nit:  Copyright in NOTICE is dated to 2019
* ran a simple flow doing site to site without issue
* verified docker build/image - looks good

Nice work, folks!  The amount of ground covered is impressive!


On Tue, Feb 23, 2021 at 2:26 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 release helper guide can be found at:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303
>
> The Git tag is minifi-cpp-0.9.0-RC2
> The Git commit ID is ae746065319c89b6df23ef6a1bd6902306087cb8
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=ae746065319c89b6df23ef6a1bd6902306087cb8
>
> Checksums of nifi-minifi-cpp-0.9.0-source.tar.gz:
> SHA256: 519bbf273cc70874a8542d7e422302731c99f44e0aa6439d0e285fbcf4a6be74
> SHA512:
> 7ebc413f0bf85d25de4e50a2ca4d68925a362f2caa1f30c53a279591dca25d4866923c28418085b8485f73c36af737cf3549ed8990977ee55e4266f8b81b08bd
>
> 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: [DISCUSS] rename master branch, look through code for other related issues

[Aldrin Piri]

+1 for making the changes.

On Wed, Jun 17, 2020 at 8:11 PM Andy LoPresto  wrote:

> I am a proponent of making this change and also using allow/deny list,
> meddler-in-the-middle, etc.
>
> Here is a blog [1] with easy instructions for executing the change in git,
> although I don’t know if there is any Apache-integration specific changes
> we would also need.
>
> [1]
> https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> He/Him
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jun 17, 2020, at 3:06 PM, Joe Witt  wrote:
> >
> > I suspect it would be fairly easy to make this change.  We do, I think,
> > have whitelist/blacklist in there somewhere but im not sure how involved.
> >
> > On Wed, Jun 17, 2020 at 3:04 PM Tony Kurc  wrote:
> >
> >> All,
> >> I've seen the discussion started on other projects [1][2], so I wanted
> to
> >> kick off a discussion to determine whether this is something nifi could
> >> look at too. Allen Wittenauer's post to yetus captures the why and some
> of
> >> the how, so rather than copy and pasting, you can take a look at what
> he's
> >> done. Thoughts?
> >>
> >> Tony
> >>
> >> 1.
> >>
> >>
> https://lists.apache.org/thread.html/rd38afa9fb6c0dcd77d1a677f1152b7398b3bda93c9106b3393149d10%40%3Cdev.yetus.apache.org%3E
> >> 2.
> >>
> >>
> https://lists.apache.org/thread.html/r0825eec0c84296bdab7cf898a987f06355443241ca02b2aaa51d3ef9%40%3Cdev.accumulo.apache.org%3E
> >>
>
>

Re: Jira contributor access

[Aldrin Piri]

Hi Wouter,

I've added you as a contributor to all the projects in the NiFi community.
We look forward to your contributions!

--aldrin

On Fri, Apr 24, 2020 at 8:03 AM Wouter de Vries 
wrote:

> Hello devs,
>
> I would like contributor access. Username: woutifier.
>
> Best regards,
>
> Wouter
>

Re: Jira, contributor access

[Aldrin Piri]

HI Peter!

I've added you as a contributor to all the projects in the NiFi community.
We look forward to your contributions!

--Aldrin

On Fri, Apr 17, 2020 at 2:58 PM Peter Gyori 
wrote:

> Dear Developers,
>
> May I ask you to grant me contributor access to the NiFi project?
> My username is: pgyori.
>
> Thanks in advance!
> Best regards,
> Peter
>

Re: Jira contributor access

[Aldrin Piri]

 Hi Lucas!

I've added you to the projects within the NiFi community.  Looking forward
to your contributions!

--Aldrin

On Thu, Apr 9, 2020 at 3:44 PM Lucas Ottersbach 
wrote:

> Hello,
>
> I would like to receive contributor access to Jira.
> My username is "EndzeitBegins".
>
> Best regards
> Lucas Ottersbach
>

Re: Jira contributor access

[Aldrin Piri]

Hi Tim,

I've added you to all of the projects in NiFi.  Looking forward to the
contributions!

--aldrin

On Sat, Apr 4, 2020 at 8:00 PM Timothy Spann 
wrote:

> Hi team,
>
> >
> > I'd like to contribute to the NiFi project. Could I get a contributor
> > access please?
> > My username is tspannhw
>
>
>
> Thanks
>
>
> Tim
>
> >
> > --
> *Tim Spann*
>  Principal DataFlow Field Engineer - 609-250-5894 -
> https://dev.to/tspannhw -
> @*PaaSDev*
> 
> [image: Cloudera][image: Cloudera on Twitter][image: Cloudera on
> Facebook][image:
> Cloudera on LinkedIn]
>

Re: Jira contributor access

[Aldrin Piri]

Hi Theo!

I've added you to the contributor role for all projects within NiFi.

Welcome and we look forward to working with you!

On Fri, Apr 3, 2020 at 1:42 PM Theo Hulscher 
wrote:

> Hello,
>
> Please grant Jira contributor access to: thulscher
> Thank you!
>
> Kind regards,
> Theo Hulscher
>

Re: [VOTE] Release Apache NiFi Registry 0.6.0

[Aldrin Piri]

I am of the opinion it is only a minor nuisance.  As it is an arg, it is
easily overridden on build (this issue is also present on the Docker Hub
item).  The script I use to publish images  explicitly provides the version
arg and would not preclude us from having an appropriately versioned image.

On Thu, Apr 2, 2020 at 4:01 PM Chris Sampson
 wrote:

> Is it a problem that you're building 0.6.0 but the docker image is
> configured for 1.0.0 (
>
> https://github.com/apache/nifi-registry/blob/master/nifi-registry-docker-maven/dockermaven/Dockerfile
> )
> as per
> https://issues.apache.org/jira/plugins/servlet/mobile#issue/NIFIREG-338?
>
>
>
> Cheers,
>
> Chris Sampson
>
> On Thu, 2 Apr 2020, 19:00 Marton Szasz,  wrote:
>
> > +1 (non-binding)
> >
> > Went through the helper guide with the correct commit ID and verified the
> > release against a minifi c++ instance.
> >
> > Thanks,
> > Marton
> >
> > On Thu, 2 Apr 2020 at 18:51, Arpad Boda 
> > wrote:
> >
> > > Thanks for pointing that out, I copied wrong ID.
> > >
> > > The correct commit ID is: 4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > > That's the commit associated with the RC tag.
> > >
> > > Dev,
> > > please use this commit ID for the release verification.
> > >
> > > Thanks,
> > > Arpad
> > >
> > >
> > >
> > > On Thu, Apr 2, 2020 at 6:41 PM Joe Witt  wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Did the usual checks and ran a live nifi against it which worked
> > > > perfectly.  Did not do secured instances though.
> > > >
> > > > Arpdad: You want to clarify the commit that the source release is
> based
> > > on
> > > > is
> > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4ddfde57f0163baa08eb782fc8be9c51d8f58af7
> > > >
> > > > That is the parent of the one you sent which has 0.6.1-SNAPSHOT.
> > > >
> > > > Thanks
> > > > Joe
> > > >
> > > > On Thu, Apr 2, 2020 at 11:54 AM Arpad Boda  wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > I am pleased to be calling this vote for the source release of
> Apache
> > > > > NiFi Registry nifi-registry-0.6.0.
> > > > >
> > > > > The source zip, including signatures, digests, etc. can be found
> at:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1160
> > > > >
> > > > > The Git tag is nifi-registry-0.6.0-RC1
> > > > > The Git commit ID is ed5c9b3f2faa8b1cab18f157b7d3263dae289aae
> > > > >
> > > > >
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=ed5c9b3f2faa8b1cab18f157b7d3263dae289aae
> > > > >
> > > > > Checksums of nifi-registry-0.6.0-source-release.zip:
> > > > > SHA256:
> > > 0ed06ef762588be0154207932d2d1ebd1266c45aed299d0fb170cbeabd4c6e2b
> > > > > SHA512:
> > > > >
> > > > >
> > > >
> > >
> >
> aa1f03c20902bf9cd94574e45cbd57526763ab135421e9d1df489cac7c487cb9c6d20ba3f6a74d7ae37b97a7de71d12edbc1c9fabf6d6b29f29397164011e097
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/aboda.asc
> > > > >
> > > > > KEYS file available here:
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > > 40 issues were closed/resolved for this release:
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12347009
> > > > >
> > > > > Release note highlights can be found here:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.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.
> > > > >
> > > > > Then please vote:
> > > > > [ ] +1 Release this package as nifi-registry-0.6.0
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because...
> > > > >
> > > >
> > >
> >
>

Re: Jira contributor access

[Aldrin Piri]

Hi Andy!

I've added you to the contributor role for all projects within NiFi.

Welcome and we look forward to working with you!

--aldrin

On Tue, Feb 25, 2020 at 2:09 PM andy naylor 
wrote:

> Nifi,
>
> I am interested in contributing to Apache Nifi, and would like contributor
> access in Jira.
> username: andy_naylor
>
> Thanks
> Andy Naylor
>

Re: Jira contributor access

[Aldrin Piri]

Hi Roberto!

I've added you to the contributor role for all projects within NiFi.

Welcome and we look forward to working with you!

--aldrin

On Mon, Feb 24, 2020 at 8:03 AM Roberto Marturano <
marturano.robe...@gmail.com> wrote:

> Dear all,
>
> I’d like to start to contribute to NiFi. I’ve some changes to propose and
> I’d like to get contributor access to JIRA.
>
> My username in Jira is: rmarturano
>
>
> Thank you very much,
> Best regards
>
> Roberto Marturano
>

Re: [VOTE] Release Apache NiFi 1.11.3

[Aldrin Piri]

Hi Otto,

Not sure we have an official way of doing this but I do a checkout of the
repo for the specified commit and run a diff of that source tree against
the specified source zip listed.

On Sat, Feb 22, 2020 at 11:13 AM Otto Fowler 
wrote:

> Joe,
> the new guide is great.  One thing that is missing, that I would like to
> make sure that I’m doing the same as you all, is how you are verifying
> the commit hashes.  Would it be possible to document how you guys are doing
> that?
>
>
> On February 21, 2020 at 22:21:41, Joe Witt (joew...@apache.org) 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...
>

Re: Minifi updates

[Aldrin Piri]

Hey Chad,

Thanks for checking in.

To the point, I think what behooves the community as a whole is to
appropriately treat MiNiFi as an assembly of NiFi given its shared core and
mitigate this dependent nature.  This effort and the work involved is
largely encapsulated by the following tickets:

* https://issues.apache.org/jira/browse/MINIFI-422 - Parent ticket to bring
these capabilities to NiFi
* https://issues.apache.org/jira/browse/MINIFI-436
* https://issues.apache.org/jira/browse/MINIFI-494
* https://issues.apache.org/jira/browse/MINIFI-481

By no means is the way it has to be accomplished.  We could likely work a
way out to get things upgraded as MINIFI-494 highlights, but being
efficient with folks' efforts, I would lean toward us taking a bit longer
and in lieu of putting time into duplicative, incremental maintenance.
Outside of all of that, if either of these approaches seem like an area you
might wish to get involved in, please feel free to drop a note on any of
the linked issues and would be happy to collaborate.

I have some additional thoughts that might take me a bit longer to compose
and may deserve a separate thread.  I'll look to get those together and
share them here for further consideration.

--aldrin

On Fri, Feb 21, 2020 at 4:17 PM Chad Zobrisky  wrote:

> Minifi is a few releases behind and was wondering if a new release was in
> the works to base line it off of a more recent nifi version.
>
> We were also looking for encrypted values for the expression language, is
> it possible to start work on moving parameter contexts into the minifi
> project? Any thoughts?
>
> Thanks,
> Chad
>

Re: Jira contributor access

[Aldrin Piri]

Hi Cameron!

I've added you to the contributor role for all projects within NiFi.

Welcome and we look forward to working with you!

--aldrin

On Fri, Feb 21, 2020 at 9:37 AM Cameron Tidd 
wrote:

> I would like to request Jira contributor access to NiFi if possible. My
> Jira username is ctidd
>
> Thanks so much!
>
> --
> Sincerely,
>
> Cameron E. Tidd
>

Re: Grant contributor access

[Aldrin Piri]

Hi Eduardo!

I've added you to the contributor role for all projects within NiFi.

Welcome and we look forward to working with you!

--aldrin

On Fri, Feb 21, 2020 at 8:31 AM Eduardo Fontes 
wrote:

> Guys,
>
> Could you please add me as a contributor in Apache NiFi'ss Jira?
> User: emfontes
>
> Thanks.
>

Re: Jira contributor access

[Aldrin Piri]

Hi Johan,

I've added you to the contributors list.  Welcome to the community and we
look forward to working with you!

aldrin

On Wed, Feb 19, 2020 at 12:07 PM johan cronsioe 
wrote:

> Hi,
>
> I would like Jira contributor access. My username is johancr.
>
> Regards,
> Johan
>

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

[Aldrin Piri]

+1, binding

notes:
* signature good
* hashes look good
* tagged commit matches
* full build with contrib check correct
* verified associated docker images functioning correctly
* ran some simple flows and verified site to site

On Sat, Feb 1, 2020 at 7:22 AM Arpad Boda 
wrote:

> +1
>
> Verified signature, hashes
> Built, started NiFi
> Created a flow
> Transmitted flowfiles from MiNiFI
>
> Although I had to skip execution of tests because of this bug:
> https://issues.apache.org/jira/browse/NIFI-7089
> The bug also appears on master as well, so it doesn't block this patch
> release.
>
>
> On Fri, Jan 31, 2020 at 9:11 PM 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)

[Aldrin Piri]

+1, binding

comments:
signature - good
hashes - good
L&N - good
built and tested some simple flows in conjunction with registry on macos,
debian

thanks for organizing, Joe!


On Wed, Jan 22, 2020 at 8:02 AM Mike Thomsen  wrote:

> +1 binding. Ran a flow with a custom processor and verified the fix for
> NIFI-7044.
>
> On Wed, Jan 22, 2020 at 3:15 AM 高橋喜秋  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/19 20:21:02, 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: [VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)

[Aldrin Piri]

+1, binding

Comments:
* signature and hashes looked good
* license and notification looked correct and comprehensive
* performed build and test successfully on Ubuntu 19.04, CentOS 7, and
MacOS 10.14
* ran a variety of flows and achieved expected results
* we should update the helper to have folks make use of the bootstrap or
enumerate the needed dependencies.  the prescribed approach worked for me
as all systems had the requisite tools and dependencies, but others may
experience trying to follow along.

Thanks for acting as RM on this release, Arpad. Lots of great work since
the last release.  Kudos to all the contributors.

On Wed, Jan 8, 2020 at 11:56 AM Arpad Boda  wrote:

> Hello Apache NiFi community,
>
> I am pleased to call this vote for the source release of Apache NiFi MiNiFi
> C++ 0.7.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.7.0/
>
> The Git tag is minifi-cpp-0.7.0-RC1
> The Git commit ID is: aa42957a2e227df41510047cece3cd606dc1cb6a
>
> Checksum of nifi-minifi-cpp-0.7.0-source.tar.gz:
> SHA256: 2a3743e809652b429f3780e616373977fb1884330adabc1430449551b6e247bc
> SHA512:
> cfa86cb3e34e1e2dc439ade2c0c389c70679a6403ebcc2befb6781995179cac3f4a8ec0e107204bcdd95f2cc6b5be67b2a7fcfe68eb87f561f209074b45fd507
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/aboda.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 144 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344866&projectId=12321520
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.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-minifi-cpp-0.7.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: Jira contributor access

[Aldrin Piri]

Hi Dayakar,

I've added you to the list of contributors.  Welcome to the community and
we look forward to your contributions!

--aldrin

On Thu, Jan 2, 2020 at 8:53 AM dayakar morem  wrote:

> Hi,
>
> I want to contribute to the Apache Nifi project so please provide
> contributor access to the jira.
>
> My jira user name: Dayakar
>
> Thanks & Regards,
> Dayakar.
>

Re: Want to be minifi committer

[Aldrin Piri]

Hi Daniel,

Glad to hear about your interest in MiNiFi!  MiNiFi's processes and
procedures are not significantly different than those of NiFi, so the
Contributor Guide [1] is a great reference point for how to engage.

As you are likely aware, we have both Java and C++ implementations.  Based
on your listed experience, it seems the Java variant would be the best for
core development, but we also have some extensions and testing code in
place that is written in Python.

You can find issues for our Java [2] and C++ [3] to see if there is
anything you would like to work on.  You mentioned some gaps that you would
like to see improved, feel free to create issues where appropriate to and
engage with the broader community via the mailing lists or on issues you
create.

Welcome to the community and we're looking forward to insights you have
regarding the medical world.  Adding to our breadth of experiences and
backgrounds helps make our project better so we are happy to have your
efforts and energies in any way you would like to apply them.  Feel free to
follow up with any additional questions and we'll be happy to help you
along your journey as best we can.

--aldrin

[1] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
[2] https://issues.apache.org/jira/projects/MINIFI
[3] https://issues.apache.org/jira/projects/MINIFICPP

On Wed, Nov 6, 2019 at 9:19 PM Daniel Wang  wrote:

> Hi NiFi developer team,
>
> I am a big data admin / developer at medical domain at MD Anderson Cancer
> Center. We have been working at data streaming for quite a while. When I do
> the use case in medical iot, I can see there are a lot of gaps between
> current minifi-nifi interaction, so I would like to join the minifi
> developer group and contribute my idea and efforts as a developer.
>
> I had years of development in Java before becoming a hadoop admin. I had
> quite some experiences coding in big data stack, including NiFi processors,
> Kafka and Spark. The primary language I am using is Java, but I also use
> Python and Scala.
>
> Anyway, can you please what is the best way to join the developer family?
> Looking forward to make a more robust minifi product that is trimmed toward
> medical IoT.
>
> Best,
> Daniel Wang
> Hadoop Admin and Big data developer
> MD Anderson Cancer Center

Re: [EXT] Re: [DISCUSS] Time based release cycles

[Aldrin Piri]

It is worth a reminder in context of this thread that the definition of a
release is well defined by the ASF [1].

Nightly builds and their ilk are explicitly intended for "the developer
community for testing purposes."  Users as folks that are contributors
testing features are the target audience.  The generalized user as a
consumer of the software would violate the linked guidance.

Other projects certainly provide these but are also quite clear on the
scope of those artifacts.  OpenOffice, as you provided, is an example of
this [2].  Not opposed to the idea as it could help with some of our build
issues, but I do not believe it alleviates the crux of what Pierre is
trying to address.

[1] https://www.apache.org/legal/release-policy.html#what
[2] https://www.openoffice.org/download/devbuilds.html

On Tue, Nov 5, 2019 at 3:06 PM Peter Wicks (pwicks) 
wrote:

> I feel like most users ask, "When is version x coming out" because they
> don't want to/or can't do a build themselves and they really want to use
> new features.
>
> I know it's a completely different direction from where I think your
> question was pointing Pierre, but I wonder how many users would be OK with
> a nightly build binary? Many other Apache projects provide nightly builds
> including JMeter, Ignite, ANT, Cordova, Solr and OpenOffice.  This would
> also make it easier for users to provide feedback sooner on changes, as
> they could just grab a pre-built binary.
>
> Thanks,
>   Peter
>
> -Original Message-
> From: Russell Bateman 
> Sent: Tuesday, November 5, 2019 8:39 AM
> To: dev@nifi.apache.org
> Subject: [EXT] Re: [DISCUSS] Time based release cycles
>
> Kafka is first-rate, rock-star technology, just as is NiFi.
>
> It would be nice to find something from Kafka elaborating on how this
> regular and accelerated release cadence is working out for them, how much
> more work it's been, what problems they've experienced, etc.
>
> I show their releases over the last couple of years as below[1]. The
> cadence appears to be settling into the the 4-month cycle proposed. It's
> possible to discern a maintenance schedule. It doesn't exactly match NiFi's
> 0.x and 1.x efforts (which were simultaneous for some time too), but it's
> clear they've faced similar complexity (maybe a little more though for a
> shorter time). And, of course, there's no meaningful way to compare the
> effort going into and features implemented in Kafka by comparison with NiFi.
>
> 2019
> 2.3.124 October
> 2.3.025 June
> 2.2.1 1 June
> 2.2.022 March
> 2.1.115 February
>
> 2018
> 2.1.020 November
> 2.0.1 9 November
> 2.0.030 July
> 1.1.119 July
> 1.0.2 8 July
> 0.11.0.3  2 July
> 0.10.2.2  2 July
> 1.1.028 March
> 1.0.1 5 March
>
> 2017
> 1.0.0 1 November
> 0.11.0.1 13 September
> 0.11.0.0 28 June
> .
> .
> .
>
> [1]
> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fkafka.apache.org%2Fdownloads&data=02%7C01%7Cpwicks%40micron.com%7C5025edaf0fcc4cd23ecb08d762064cb5%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C1%7C637085651507559851&sdata=ax5RXiprNm8Ls1k%2FuEE4SwA5tCXzObJu3Dk%2FiP3h3dI%3D&reserved=0
>
> On 11/5/19 8:02 AM, Pierre Villard wrote:
> > Hi NiFi dev community,
> >
> > We just released NiFi 1.10 and that's an amazing release with a LOT of
> > great new features. Congrats to everyone!
> >
> > I wanted to take this opportunity to bring a discussion around how
> > often we're doing releases.
> >
> > We released 1.10.0 yesterday and we released 1.9.0 in February, that's
> > around 8 months between the two releases. And if we take 1.9.2,
> > released early April, that's about 7 months.
> >
> > I acknowledge that doing releases is really up to the committers and
> > anyone can take the lead to perform this process, however, we often
> > have people asking (on the mailing lists or somewhere else) about when
> > will the next release be. I'm wondering if it would make sense to
> > think about something a bit more "planned" by doing time based releases.
> >
> > The Apache Kafka community wrote a nice summary of the pros/cons about
> > such an approach [1] and it definitely adds more work to the
> > committers with more frequent releases. I do, however, think that it'd
> > ease the adoption of NiFi, its deployment and the dynamism in PR/code
> review.
> >
> > I'm just throwing the idea here and I'm genuinely curious about what
> > you think about this approach.
> >
> > [1]
> > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik
> > i.apache.org%2Fconfluence%2Fdisplay%2FKAFKA%2FTime%2BBased%2BRelease%2
> > BPlan&data=02%7C01%7Cpwicks%40micron.com%7C5025edaf0fcc4cd23ecb08d
> > 762064cb5%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C1%7C637085651507559
> > 851&sdata=Nj1t2mTP7VWwOIxD5V5vlnH8quyXYP8ul6Sa2e3nswE%3D&reser
> > ved=0
> >
> > Thanks,
> > Pierre
> >
>
>

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

[Aldrin Piri]

+1, binding

comments:
verified hashes and signature
verified build and tests on Debian 10 and macOS 10.14.6.  Needed to update
my /etc/hosts to get the Kudu suite of tests to pass
L&N looked good
verified integration with MiNiFi in a test environment and basic flow
versioning functionality

On Fri, Nov 1, 2019 at 12:22 PM Scott Aslan  wrote:

> +1 (binding)
>
> Verified signatures, hashes, build, etc. Tested various parameter use
> cases.
>
> Thanks for RMing Joe!
>
> On Fri, Nov 1, 2019 at 10:40 AM Matt Burgess  wrote:
>
> > +1 (binding)
> >
> > Ran thru the release helper and tried a number of flows with various
> > controller services and processors, LGTM
> >
> > Thanks for RM'ing Joe!
> >
> > On Tue, Oct 29, 2019 at 1:32 PM Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > nifi-1.10.0.
> > >
> > > As they say 'third time's a charm'.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1151
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.10.0/
> > >
> > > The Git tag is nifi-1.10.0-RC3
> > > The Git commit ID is b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> > >
> > > Checksums of nifi-1.10.0-source-release.zip:
> > > SHA256:
> e9b0a14b3029acd69c6693781b6b6487c14dda12676db8b4a015bce23b1029c1
> > > SHA512:
> > >
> >
> b07258cbc21d2e529a1aa3098449917e2d059e6b45ffcfcb6df094931cf16caa8970576555164d3f2290cfe064b5780ba1a8bf63dad04d20100ed559a1cfe133
> > >
> > > 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
> > >
> > > 384 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12344993
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.10.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.10.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
>

[ANNOUNCE] New Apache NiFi Committer Dániel Bakai

[Aldrin Piri]

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

[ANNOUNCE] New Apache NiFi Committer Kotaro Terada

[Aldrin Piri]

Apache NiFi community,

On behalf of the Apache NiFI PMC, I am very pleased to announce that Kotaro
has accepted the PMC's invitation to become a committer on the Apache NiFi
project. We greatly appreciate all of Kotaro's hard work and generous
contributions to the project. We look forward to continued involvement
in the project.

Kotaro contributed to a breadth of areas in both NiFi and Registry as well
as
being a regular reviewer of our releases. Kotaro's communication in Jira
issues
and responsiveness to the review processes highlighted great collaboration
and
embodied our community goals for the project.

Welcome and congratulations!

--ap

Re: Fix slack invite link ?

[Aldrin Piri]

Good idea, Kevin.  Fairly certain I can make this work with the ASF URL
shortener.  Will set things up using that path.

On Wed, Oct 23, 2019 at 12:48 PM Kevin Doran  wrote:

> If it is going to change periodically, could we setup a stable URL a
> web host (ideally nifi.apache.org) that redirects to the "currently
> active" updatable URL, so that the updates only need to be made in one
> place in the future. I'm not familiar with how our website is
> published/hosted and how much control we have over that server infra,
> if any, so maybe this is a request we would have to bring to ASF
> infra.
>
> On Wed, Oct 23, 2019 at 11:36 AM Aldrin Piri  wrote:
> >
> > Link is updated:
> >
> https://join.slack.com/t/apachenifi/shared_invite/enQtNDI2NDMyMTY3MTA5LTQ0YmQwMjljZDQ4NjkzODI0ZWU1YmU0YmU0YjJiNjVjMjhmMWQwZjY0Njk0NDY1OTlkMjM5NmNiODg4MGFmYWU
> >
> > Slack simultaneously says "For security, invite links will expire and can
> > be used by up to 2000 people." and "This link doesn't expire. Need to
> > change this? Deactivate your link and choose a new duration." so this may
> > be a periodic task.
> >
> > Changes are also pushed to nifi-site git and deployed to the site.
> >
> > On Wed, Oct 23, 2019 at 10:16 AM Aldrin Piri 
> wrote:
> >
> > > Will do it.
> > >
> > > On Wed, Oct 23, 2019 at 10:01 AM Joe Witt  wrote:
> > >
> > >> Team,
> > >>
> > >> Got a note from
> > >>
> > >> The slack invite link at https://nifi.apache.org/mailing_lists.html
> is
> > >> dead. Can you  share a new one with me, and maybe update the one on
> the
> > >> website?
> > >>
> > >> Sorry if you aren’t the right person to contact about this.
> > >>
> > >>
> > >>
> > >> All the best,
> > >>
> > >> José Vieira
> > >>
> > >>
> > >> Is there anyone available that can look into/solve this?
> > >>
> > >> Thanks
> > >>
> > >> Joe
> > >>
> > >
>

Re: Fix slack invite link ?

[Aldrin Piri]

Link is updated:
https://join.slack.com/t/apachenifi/shared_invite/enQtNDI2NDMyMTY3MTA5LTQ0YmQwMjljZDQ4NjkzODI0ZWU1YmU0YmU0YjJiNjVjMjhmMWQwZjY0Njk0NDY1OTlkMjM5NmNiODg4MGFmYWU

Slack simultaneously says "For security, invite links will expire and can
be used by up to 2000 people." and "This link doesn't expire. Need to
change this? Deactivate your link and choose a new duration." so this may
be a periodic task.

Changes are also pushed to nifi-site git and deployed to the site.

On Wed, Oct 23, 2019 at 10:16 AM Aldrin Piri  wrote:

> Will do it.
>
> On Wed, Oct 23, 2019 at 10:01 AM Joe Witt  wrote:
>
>> Team,
>>
>> Got a note from
>>
>> The slack invite link at https://nifi.apache.org/mailing_lists.html is
>> dead. Can you  share a new one with me, and maybe update the one on the
>> website?
>>
>> Sorry if you aren’t the right person to contact about this.
>>
>>
>>
>> All the best,
>>
>> José Vieira
>>
>>
>> Is there anyone available that can look into/solve this?
>>
>> Thanks
>>
>> Joe
>>
>

Re: Fix slack invite link ?

[Aldrin Piri]

Drat.  Will take care of those as well.  Thanks for pointing them out.

On Wed, Oct 23, 2019 at 11:27 AM Pierre Villard 
wrote:

> To be updated on the README.md files as well (badges).
>
> Le mer. 23 oct. 2019 à 16:16, Aldrin Piri  a écrit :
>
> > Will do it.
> >
> > On Wed, Oct 23, 2019 at 10:01 AM Joe Witt  wrote:
> >
> > > Team,
> > >
> > > Got a note from
> > >
> > > The slack invite link at https://nifi.apache.org/mailing_lists.html is
> > > dead. Can you  share a new one with me, and maybe update the one on the
> > > website?
> > >
> > > Sorry if you aren’t the right person to contact about this.
> > >
> > >
> > >
> > > All the best,
> > >
> > > José Vieira
> > >
> > >
> > > Is there anyone available that can look into/solve this?
> > >
> > > Thanks
> > >
> > > Joe
> > >
> >
>

Re: Fix slack invite link ?

[Aldrin Piri]

Will do it.

On Wed, Oct 23, 2019 at 10:01 AM Joe Witt  wrote:

> Team,
>
> Got a note from
>
> The slack invite link at https://nifi.apache.org/mailing_lists.html is
> dead. Can you  share a new one with me, and maybe update the one on the
> website?
>
> Sorry if you aren’t the right person to contact about this.
>
>
>
> All the best,
>
> José Vieira
>
>
> Is there anyone available that can look into/solve this?
>
> Thanks
>
> Joe
>

Re: Apache NIFI Contributor Access

[Aldrin Piri]

Hi Shayne,

Welcome!  I've added you to the contributor role.  Please let us know if
you have any issues with assigning issues to yourself.

--aldrin

On Fri, Oct 4, 2019 at 1:41 PM Shayne Burgess 
wrote:

> I would like to begin to contribute to Apache NIFI and be able to get
> issues assigned to me in Jira. Can I be given contributor access so that I
> can do that? If there is another process I should follow to get access just
> let me know.
>
>
> My username is "sburges".
>
>
> Thanks,
>
> Shayne
>

Re: hello, I have some doubts about the certification configuration of minifi-c2

[Aldrin Piri]

Hi there,

The DN would be specified by the certificate provisioned as part of a mutual 
auth setup between the C2 server and one or more minifi instances. This 
information is provided to the server as part of the handshake and allows the 
server to extract out the relevant details and pass that through its 
authorization filters. 

> On Sep 25, 2019, at 23:06, 王谭旭  wrote:
> 
> hello
> I have some doubts about the certification configuration of 
> minifi-c2(./conf/authorities.yaml、./conf/authorizations.yaml).
> So says the official documentation for minifi-c2: "./conf/authorities.yaml 
> determines the authority or authorities (arbitrary string value) to assign to 
> requesters based on their DN." My question is how does the requester 
> configure his own dn? How does c2 receive the requester's dn?
> I would appreciate it if you could answer my question.

Re: [VOTE] Create NiFi Standard Libraries sub-project

[Aldrin Piri]

+1, binding

On Tue, Sep 3, 2019 at 19:46 Yolanda Davis 
wrote:

> +1 Create NiFi Standard Libraries (binding)
>
> On Tue, Sep 3, 2019 at 7:03 PM Koji Kawamura 
> wrote:
>
> > +1 Create NiFi Standard Libraries (binding)
> >
> > On Wed, Sep 4, 2019 at 7:25 AM Mike Thomsen 
> > wrote:
> > >
> > > +1 binding
> > >
> > > On Tue, Sep 3, 2019 at 5:33 PM Andy LoPresto 
> > wrote:
> > >
> > > > +1, create NiFi Standard Libraries (binding)
> > > >
> > > > Andy LoPresto
> > > > alopre...@apache.org
> > > > alopresto.apa...@gmail.com
> > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > > >
> > > > > On Sep 3, 2019, at 2:16 PM, Bryan Bende  wrote:
> > > > >
> > > > > All,
> > > > >
> > > > > In a previous thread there was a plan discussed to restructure some
> > of
> > > > > the repositories in order to address several different issues, such
> > as
> > > > > build time, reusability of code, and eventually separating how the
> > > > > framework and extensions are released [1][2].
> > > > >
> > > > > The overall plan requires many steps to get there, so I'd like to
> > > > > propose starting with a small actionable step - the creation of a
> new
> > > > > sub-project called NiFi Standard Libraries (formerly referred to as
> > > > > nifi-commons).
> > > > >
> > > > > Project Name: Apache NiFi Standard Libraries
> > > > > Git Repository: nifi-standard-libraries
> > > > > JIRA: NIFILIBS
> > > > >
> > > > > Description:
> > > > >
> > > > > A collection of standard implementations used across the NiFi
> > ecosystem.
> > > > >
> > > > > Candidate Libraries:
> > > > >
> > > > > In general, each library may consist of multiple Maven modules, and
> > > > > should be independent from the rest of the ecosystem, and from
> other
> > > > > libraries within NiFi Standard Libraries.
> > > > >
> > > > > In addition, each library may make it's own decision about whether
> it
> > > > > is considered a public facing extension point/API, or an internal
> > > > > library that may be changed at any time. This should be documented
> in
> > > > > a README at the root of each library, such as
> > > > > nifi-standard-libraries/nifi-xyz/README.
> > > > >
> > > > > An initial library that has been discussed was referred to as
> > > > > 'nifi-security' and would centralize much of the security related
> > code
> > > > > shared by NiFi and NiFi Registry, such as shared security APIs, and
> > > > > implementations for various providers, such as LDAP/Kerberos/etc.
> > > > >
> > > > > A second candidate library would be an optimistic-locking library
> > > > > based on NiFi's revision concept. Currently this has been created
> > > > > inside nifi-registry for now [3], but could be moved as soon as
> > > > > nifi-standard-libraries exists.
> > > > >
> > > > > (This list does not have to be final in order to decide if we are
> > > > > creating NiFi Standard Libraries or not)
> > > > >
> > > > > Integration & Usage:
> > > > >
> > > > > Once NiFi Standard Libraries is created, the community can start
> > > > > creating and/or moving code there and perform releases as
> necessary.
> > A
> > > > > release will consist of the standard Apache source release, plus
> > > > > artifacts released to Maven central. The community can then decide
> > > > > when it is appropriate to integrate these released libraries into
> one
> > > > > of our downstream projects.
> > > > >
> > > > > For example, if we create a nifi-security library in
> > > > > nifi-standard-libraries, we can release that whenever we decide,
> but
> > > > > we may not integrate it into NiFi or NiFi Registry until it makes
> > > > > sense for a given release of those projects.
> > > > >
> > > > > This vote will be open for 48 hours, please vote:
> > > > >
> > > > > [ ] +1 Create NiFi Standard Libraries
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not create NiFi Standard Libraries because...
> > > > >
> > > > > [1]
> > > >
> >
> http://apache-nifi.1125220.n5.nabble.com/discuss-Splitting-NiFi-framework-and-extension-repos-and-releases-td27499.html
> > > > > [2]
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/NiFi+Project+and+Repository+Restructuring
> > > > > [3]
> > > >
> >
> https://github.com/apache/nifi-registry/tree/master/nifi-registry-core/nifi-registry-revision
> > > >
> > > >
> >
>
>
> --
> --
> yolanda.m.da...@gmail.com
> @YolandaMDavis
>

Re: [discuss] approaching a NiFi 1.10.0 release

[Aldrin Piri]

I created NIFI-6604 [1] to reduce assembly size and listed it as a Blocker
for this release.  The issue has a link to the associated discussion thread
and an initial PR.

--aldrin

[1] https://issues.apache.org/jira/browse/NIFI-6604

On Thu, Aug 29, 2019 at 4:08 PM Matt Burgess  wrote:

> Mike,
>
> I’ll review those two graph PRs tonight or tomorrow (if they’re still open
> by then)
>
> > On Aug 29, 2019, at 3:43 PM, Mike Thomsen 
> wrote:
> >
> > I have two open graph-related PR's that are really small and are needed
> to
> > close some bugs that will be bad for early adopters:
> >
> > https://github.com/apache/nifi/pull/3571
> > https://github.com/apache/nifi/pull/3572
> >
> > If someone wants to review, that'd be great. Otherwise, I can merge them
> in
> > because I'm doing daily work on some graph stuff using a branch based on
> > both patches.
> >
> > Thanks,
> >
> > Mike
> >
> >> On Thu, Aug 29, 2019 at 2:12 PM Joe Witt  wrote:
> >>
> >> We had another discuss on that recently and the intent is to drop a few
> >> toys off the raft and update migration guidance.
> >>
> >> Thanks
> >>
> >>> On Thu, Aug 29, 2019 at 2:02 PM Jeremy Dyer  wrote:
> >>>
> >>> +1 looking forward to this.
> >>>
> >>> I recall seeing some issues about Apache Infra and the binary size.
> Were
> >>> all of those appropriate modules removed as discussed and the build
> size
> >>> will be small enough now?
> >>>
>  On Thu, Aug 29, 2019 at 1:35 PM Bryan Bende  wrote:
> 
>  +1 Looking forward to getting parameters and Java 11 support out there
>  in a release.
> 
> > On Thu, Aug 29, 2019 at 1:02 PM Joe Witt  wrote:
> >
> > Team,
> >
> > It looks like we're reaching a point in which it is time to close in
> >> on
> > 1.10.
> >
> >
> 
> >>>
> >>
> https://issues.apache.org/jira/browse/NIFI-6595?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.10.0
> >
> > There are 250+ issues in there nearly 240 of which are already
>  resolved.  I
> > haven't gone through yet for fully analyzing but the awesome Java 11
> >>> work
> > Jeff Storck and others has done means we can now build on Java 11 as
> >>> well
> > as run on it.  There is a ton of great work on parameters which will
> >>> make
> > managing flows at scale much easier.  We will need to drop some nars
>  which
> > means we have some migration guidance to update.
> >
> > I'd like to volunteer as RM but if there are any other takers please
> >>> let
>  me
> > know.
> >
> > As we close in on releases this tends to create a lot of urgency to
>  quickly
> > try to get new things in.  I will try to manage this well.  As always
> >>> we
> > can do another release.  There is no timeline pushing us to have such
>  gaps
> > between releases...we can always do another feature release.  That
> >>> said,
>  PR
> > review bandwidth is at a super premium.  We receive a lot more PRs
> >> than
>  we
> > do receive reviews.  We'll have to work this as the PR depth grows.
> >
> > Thanks
> > Joe
> 
> >>>
> >>
>

Re: [VOTE] Release Apache NiFi Registry 0.5.0

[Aldrin Piri]

+1, binding

comments:
hashes and signature good
build and tests good
L&N good
verified integration and basic flow versioning functionality

On Fri, Aug 23, 2019 at 4:15 PM Marc Parisi  wrote:

> +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: [DISCUSS] Assembly size for 1.10

[Aldrin Piri]

release.
> > > > > >
> > > > > > On Wed, Aug 21, 2019 at 6:22 PM Mike Thomsen <
> mikerthom...@gmail.com
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Another factor on why that would be a good idea: I might soon
> have
> > > to
> > > > > > pivot
> > > > > > > and do the R&D on adding dgraph support to graph bundle. So
> it's
> > > not
> > > > > > > altogether unlikely that it might need to be refactored to make
> > > room
> > > > > for
> > > > > > > other graph tech.
> > > > > > >
> > > > > > > On Wed, Aug 21, 2019 at 6:20 PM Mike Thomsen <
> > > mikerthom...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Go ahead and remove the whole graph bundle from the
> assembly. I
> > > > would
> > > > > > > > recommend cutting a release of it separately and putting it
> up on
> > > > > > > GitHub's
> > > > > > > > releases listing if that's a possibility for us/INFRA w/
> GitHub.
> > > > Most
> > > > > > of
> > > > > > > > our potential graph users are savvy enough that if add a few
> > > > steps, I
> > > > > > > don't
> > > > > > > > see it causing any grief on them getting it stood up and
> giving
> > > us
> > > > > > > feedback.
> > > > > > > >
> > > > > > > > Might be a good idea also to add a "full-build" profile to
> the
> > > > > assembly
> > > > > > > so
> > > > > > > > that we can throw the whole kitchen sink into an unofficial
> build
> > > > if
> > > > > we
> > > > > > > > build it ourselves for someone else.
> > > > > > > >
> > > > > > > > On Wed, Aug 21, 2019 at 3:09 PM Joe Witt  >
> > > > wrote:
> > > > > > > >
> > > > > > > >> Bryan
> > > > > > > >>
> > > > > > > >> I agree with all of that.  What does that get us to?
> > > > > > > >>
> > > > > > > >> Thanks
> > > > > > > >>
> > > > > > > >> On Wed, Aug 21, 2019 at 3:03 PM Bryan Bende <
> bbe...@gmail.com>
> > > > > wrote:
> > > > > > > >>
> > > > > > > >> > I would vote to make nifi-flume-nar optional, and it looks
> > > like
> > > > > > > >> > nifi-other-graph-services-nar might be new since last
> release,
> > > > so
> > > > > > > >> > since that is in the top 10 and not released yet, it might
> > > also
> > > > > be a
> > > > > > > >> > good candidate (not downplaying the usefulness of
> anything in
> > > > that
> > > > > > > >> > NAR).
> > > > > > > >> >
> > > > > > > >> > I would also think we could consider the
> nifi-kafka-0-8-nar
> > > > since
> > > > > > > >> > Kafka 0.8 is quite old at this point, and we already have
> > > other
> > > > > > Kafka
> > > > > > > >> > NARs for 0.9, 0.10, 0.11, 1.0, and 2.0. Might even
> consider
> > > > > > dropping a
> > > > > > > >> > few more versions from default assembly.
> > > > > > > >> >
> > > > > > > >> > On Wed, Aug 21, 2019 at 2:45 PM Aldrin Piri <
> > > ald...@apache.org>
> > > > > > > wrote:
> > > > > > > >> > >
> > > > > > > >> > > Hi folks,
> > > > > > > >> > >
> > > > > > > >> > > Doing a recent PR review and build, it seems that
> master has
> > > > > > amassed
> > > > > > > >> some
> > > > > > > >> > > additional size since our 1.9.2 release approaching
> 200MB.
> > > > > > > >> &g

[DISCUSS] Assembly size for 1.10

[Aldrin Piri]

Hi folks,

Doing a recent PR review and build, it seems that master has amassed some
additional size since our 1.9.2 release approaching 200MB.

Unfortunately, this is problematic and needs to be addressed in advance of
our 1.10 release.  INFRA has been more than helpful making one off
exceptions [1][2] for the larger assembly to get published to the ASF
repository and its associated mirrors, but another release that is even
larger is not something we can allow.  In a Linux environment, the master
build reports in at 1575671276 which puts us over the hard limit
highlighted in [2].

We had a prior community discussion [3] about splitting the framework and
extension repos and I am hoping to revive that discussion, in part.  We
certainly know what our longer term goals and ambitions are but need a fix
in the interim.  In the current state, we will not be able to make our
convenience binaries available at the conclusion of the release process.

At minimum we should evaluate which bundles are eligible to get treated as
optional dependencies and only enabled via profile, much like the work that
has occurred surrounding some of our other, hefty NARs. [4] A listing of
the top 50 largest NARs, excluding framework and standard, is available in
a gist [5].  The nifi-media-nar looks to be a good initial candidate for
exclusion.

Thanks for your consideration!

--aldrin

[1] https://issues.apache.org/jira/browse/INFRA-11252
[2] https://issues.apache.org/jira/browse/INFRA-15816
[3]
https://lists.apache.org/thread.html/939a7630a2e32594cd10444e48b7a1321fd9ce51834d911a8c04b6a9@
[4]
https://github.com/apache/nifi/blob/master/nifi-assembly/pom.xml#L807-L875
[5] https://gist.github.com/apiri/4d9a02f9f6b46867b601956df83b6d8c

Re: [jira] [Created] (MINIFI-506) Change minifi-assembly antrun "tasks" tags to "target"

[Aldrin Piri]

Please make use of the "unsubscribe" address
commits-unsubscr...@nifi.apache.org.

All lists and their respective subscribe/unsubscribe addresses are
available at https://nifi.apache.org/mailing_lists.html

On Thu, Jul 11, 2019 at 11:46 AM Zaminah Williams <
zwilli...@onyxconsults.com> wrote:

> Can you please send instructions on how I can be removed from this alias?
> It has been going to a SPAM folder and it is at capacity.
>
>
> Zaminah D Williams
>
> Onyx Consulting Services, LLC
>
> President/CEO
>
> (410) 814-7651 (o)
>
> (301) 467-6680 (c)
>
>
> 
> From: Aldrin Piri (JIRA) 
> Sent: Thursday, July 11, 2019 9:34 AM
> To: comm...@nifi.apache.org
> Subject: [jira] [Created] (MINIFI-506) Change minifi-assembly antrun
> "tasks" tags to "target"
>
> Aldrin Piri created MINIFI-506:
> --
>
>  Summary: Change minifi-assembly antrun "tasks" tags to
> "target"
>  Key: MINIFI-506
>  URL: https://issues.apache.org/jira/browse/MINIFI-506
>  Project: Apache NiFi MiNiFi
>   Issue Type: Improvement
>   Components: Build
> Reporter: Aldrin Piri
> Assignee: Aldrin Piri
>  Fix For: 0.6.0
>
>
> "tasks" is deprecated as per the plugin.
>
> [WARNING] Parameter tasks is deprecated, use target instead
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v7.6.14#76016)
>

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

[Aldrin Piri]

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 
> > 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 
> > >> 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
> > >>>>
> > >>>
> > >>
> >
>

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

[Aldrin Piri]

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  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 
>> 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
 
>>> 
>> 

[ANNOUNCE] New Apache NiFi PMC member Peter Wicks

[Aldrin Piri]

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

[ANNOUNCE] New Apache NiFi Committer Arpad Boda

[Aldrin Piri]

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 Registry 0.4.0

[Aldrin Piri]

+1, binding

notes:
Signature and hashes looked good
Correct hash used for source release
Build, tests, and integration tests all good
Verified basic functionality with a NiFi instance.

I did see there was a duplicate entry for Querystring.  This is captured in
https://issues.apache.org/jira/browse/NIFIREG-273



On Thu, May 16, 2019 at 6:05 PM Kevin Doran  wrote:

> +1 (binding)
>
> Followed the steps in the release helper's guide.
>
> One minor thing I noticed was that a few dates in the
> nifi-registry-assembly NOTICE file need to be updated (the source
> NOTICE looks good though).
>
> There are a ton of great improvements in this release. Nice work
> everyone, and thanks for RM'ing, Bryan!
> Kevin
>
> On Thu, May 16, 2019 at 5:36 PM Bryan Bende  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi Registry nifi-registry-0.4.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1145
> >
> > The Git tag is nifi-registry-0.4.0-RC1
> > The Git commit ID is 4d7add09cd915b20dcc9959b49ecdf202d5eac2a
> >
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4d7add09cd915b20dcc9959b49ecdf202d5eac2a
> >
> > Checksums of nifi-registry-0.4.0-source-release.zip:
> > SHA256: a8753372fbc24f7d293df6205c465edee7a4167d835811e84e27df3e609d2be1
> > SHA512:
> 70ade1ba2dcf5363b6568669080a3607e5dfd3dffd28651ba5f6961db835e0f61ff7f9758757358800774e4e1063cdcfdd5d44a712a845e34052544cfce9b047
> >
> > 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
> >
> > 37 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12344183
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.4.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.
> > Then please vote:
> >
> > [ ] +1 Release this package as nifi-registry-0.4.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

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

[Aldrin Piri]

+1, binding

notes:
signature and hashes good
source matched listed commit
build good
performed build of NiFi using empty Maven repo.  NARs included the
anticipated descriptor file and their contents looked good
NiFi ran as expected

On Fri, May 10, 2019 at 1:47 AM Koji Kawamura 
wrote:

> +1 (binding)
>
> Went through the Release Helper Guide.
> - On OS X
> - Build nifi-nar-maven-plugin with contrib-check was successful
> - Removed .m2 dir before building NiFi
> - Full NiFi build was successful
> - Tested standalone and secure clustered NiFi, worked as expected
> - Confirmed extension-manifest.xml files were generated and contained in
> nars
>
> Thanks Bryan for RMing!
>
> Koji
>
> On Fri, May 10, 2019 at 3:52 AM Bryan Bende  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi NAR Maven Plugin 1.3.1.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1144
> >
> > The Git tag is nifi-nar-maven-plugin-1.3.1-RC1
> > The Git commit ID is 51deb8a070ef2b9f0041c2b6448b72de67f91822
> >
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=51deb8a070ef2b9f0041c2b6448b72de67f91822
> >
> > Checksums of nifi-nar-maven-plugin-1.3.1-source-release.zip:
> > SHA256: 48f2b3e361d7e45c79a659bfcf7a56a88278411f3686d2da800c58858c742637
> > SHA512:
> c0ace13e7d7f7dd4468c7ac71f1dddc098393481cd1096c7479a48fb215ef47197969da50edb987b182592b988368104d58ec26a21ba4beea2a4db46b6dca4eb
> >
> > 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
> >
> > 1 issue was closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345484&styleName=&projectId=12316020
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.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-nar-maven-plugin-1.3.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

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

[Aldrin Piri]

+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: [VOTE] Release Apache NiFi MiNiFi C++ 0.6.0 (RC2)

[Aldrin Piri]

+1, binding

So much great stuff in this release.  Thanks for RMing, Marc!

comments:
Signature and hashes looked good
Verified build, tests, and linter looked good on Ubuntu 18 and OS X 10.13
Performed builds using the make targets {u16, u18, centos, debian, fedora}
to generate successful assemblies
Verified a sampling of the assemblies on different platforms and worked as
expected for a variety of flows and functionalities







On Tue, Mar 19, 2019 at 12:52 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-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=
> <
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=28ade6cf75e8a0ccce78699f147f4ad9baaf70c2
> >
> 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...
>

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

[Aldrin Piri]

+1, binding

comments:
hashes and signature looked good
build, tests, and contrib check good on Ubuntu and MacOS


On Thu, Mar 14, 2019 at 6:58 PM James Wing  wrote:

> +1 (binding) - Ran through the release helper, checked the signatures,
> license/readme, and ran the full build.  Ran a simple test flow.
>
> Thanks, Joe, for putting this release together!
>
> On Tue, Mar 12, 2019 at 10:49 PM Joe Witt  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.9.1.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1138
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.9.1-rc1/
> >
> > The Git tag is nifi-1.9.1-RC1
> > The Git commit ID is a5cedc4ad39b17bee97303b63b620f9ac3dddc79
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=a5cedc4ad39b17bee97303b63b620f9ac3dddc79
> >
> > Checksums of nifi-1.9.1-source-release.zip:
> > SHA256: 7099abb33e26445788630b69f38b8788117cdd787b7001752b4893d8b6c16f38
> > SHA512:
> >
> >
> 678c2ee32f7db8c73393178f329c574315b1b892084b822f9b7a6dc5bc159d5e7e1169812d9676a72f738d03fd2f4366f2b67ddee152b56c8a77751fd5cbb218
> >
> > 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
> >
> > 19 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345163
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.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.9.1
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: Docker build broken for me in 1.9.1RC2

[Aldrin Piri]

Interestingly enough, I had started another build from where that one
failed using resume from.  That worked and generated the images which seems
to function appropriately.  Gives a bit more credence to the possible
naughtiness on the behalf of the plugin.

On Thu, Mar 14, 2019 at 10:03 AM Aldrin Piri  wrote:

> That is interesting.  Seems like the plugin may possibly be doing
> mischievous things with how it handles some of our libraries in the
> associated build context.  Several of these libs, presumably, are also
> those we adjusted in NIFI recently.
>
> I think this is okay to adjust after the release as this shouldn't
> preclude us from having a Docker image given its reliance only on a
> successful assembly from the RC process.  However, I do also see issue in
> the build with the profile activated.
>
> On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen 
> wrote:
>
>> mvn clean install -Pdocker
>>
>> Throws the following error:
>>
>> [WARNING] An attempt failed, will retry 1 more times
>> org.apache.maven.plugin.MojoExecutionException: Could not build image
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
>> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
>> at
>>
>> com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
>> at
>>
>> com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
>> at
>>
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
>> at
>>
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
>> at
>>
>> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
>> at
>>
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>>
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at
>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
>> at
>>
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
>> Caused by: com.spotify.docker.client.exceptions.DockerException:
>>
>> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
>> Can not construct instance of
>> com.spotify.docker.client.messages.RegistryAuth: no String-argument
>> constructor/factory method to deserialize from String value ('swarm')
>>  at [Source: N/A; line: -1, column: -1] (through reference chain:
>> java.util.LinkedHashMap["stackOrchestrator"])
>> at
>>
>> com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
>> at
>>
>> com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
>> at
>>
>> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
>> at
>>
>> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
>> at
>> com.spotify.plugin.dockerfile.BuildMojo.buildI

Re: Docker build broken for me in 1.9.1RC2

[Aldrin Piri]

That is interesting.  Seems like the plugin may possibly be doing
mischievous things with how it handles some of our libraries in the
associated build context.  Several of these libs, presumably, are also
those we adjusted in NIFI recently.

I think this is okay to adjust after the release as this shouldn't preclude
us from having a Docker image given its reliance only on a successful
assembly from the RC process.  However, I do also see issue in the build
with the profile activated.

On Thu, Mar 14, 2019 at 9:18 AM Mike Thomsen  wrote:

> mvn clean install -Pdocker
>
> Throws the following error:
>
> [WARNING] An attempt failed, will retry 1 more times
> org.apache.maven.plugin.MojoExecutionException: Could not build image
> at
> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:185)
> at com.spotify.plugin.dockerfile.BuildMojo.execute(BuildMojo.java:105)
> at
>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.tryExecute(AbstractDockerMojo.java:227)
> at
>
> com.spotify.plugin.dockerfile.AbstractDockerMojo.execute(AbstractDockerMojo.java:216)
> at
>
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
>
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
>
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
>
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:191)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
>
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: com.spotify.docker.client.exceptions.DockerException:
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
> Can not construct instance of
> com.spotify.docker.client.messages.RegistryAuth: no String-argument
> constructor/factory method to deserialize from String value ('swarm')
>  at [Source: N/A; line: -1, column: -1] (through reference chain:
> java.util.LinkedHashMap["stackOrchestrator"])
> at
>
> com.spotify.docker.client.auth.ConfigFileRegistryAuthSupplier.authForBuild(ConfigFileRegistryAuthSupplier.java:102)
> at
>
> com.spotify.docker.client.auth.MultiRegistryAuthSupplier.authForBuild(MultiRegistryAuthSupplier.java:77)
> at
>
> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1388)
> at
>
> com.spotify.docker.client.DefaultDockerClient.build(DefaultDockerClient.java:1365)
> at
> com.spotify.plugin.dockerfile.BuildMojo.buildImage(BuildMojo.java:178)
> ... 25 more
> Caused by:
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException:
> Can not construct instance of
> com.spotify.docker.client.messages.RegistryAuth: no String-argument
> constructor/factory method to deserialize from String value ('swarm')
>  at [Source: N/A; line: -1, column: -1] (through reference chain:
> java.util.LinkedHashMap["stackOrchestrator"])
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.JsonMappingException.from(JsonMappingException.java:270)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:1456)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleMissingInstantiator(DeserializationContext.java:1012)
> at
>
> com.spotify.docker.client.shaded.com.fasterxml.jackson.databind.deser.ValueInstantiator._createFromStringFallbac

Re: NiFi and MiNiFi Compatability?

[Aldrin Piri]

Hi Jon,

When you say point against the latest version of NiFi, I'm going to assume
you are talking about the transmission of data across Site to Site.  From
that standpoint, there are no issues.

What can be problematic is the reusing of NARs in MiNiFi depending on
framework level changes that may occur in the API.

There is an effort underway to make MiNIFi a specialized assembly of NiFi
to more tightly integrate its usage of the core NiFi libraries it is
already making use of.  This is captured in MINIFI-422 [1].  Typically,
several folks in the community have bespoke flows and configurations that
they use to verify these interactions as parts of both releases in addition
to some of the integration tests in the MiNiFI codebase itself.

Let me know if there are other questions or areas of clarification needed.

--aldrin

[1] https://issues.apache.org/jira/browse/MINIFI-422

On Mon, Mar 11, 2019 at 8:38 PM Jon Logan  wrote:

> Hi All,
>
> I was wondering if there are compatibility concerns between NiFi and
> MiNiFi? Specifically, it seems like the last release of MiNiFi is against
> 1.7 -- should we expect problems if we were to point this against the
> latest version of NiFi?
>
> If so, are there any plans of trying to coordinate releases between the
> project and sub-project, even if its just to link against the same
> binaries? I was also curious if MiNiFi compatibility is considered during
> the NiFi release / testing process?
>
>
> Thanks!
> Jon
>

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

[Aldrin Piri]

Sounds great to me.  Definitely have put a lot of great advances since our
last release in both features and robustness.  Looking forward to it and
thanks for volunteering for RM duties.

On Tue, Mar 5, 2019 at 9:40 AM Kevin Doran  wrote:

> Wow, that list of features is impressive, and certainly I agree it
> would be great to get them all in a release. Thanks for kicking it
> off, Marc!
>
> Regards,
> Kevin
>
> On Tue, Mar 5, 2019 at 8:41 AM Marc Parisi  wrote:
> >
> > 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: [VOTE] Release Apache NiFi 1.9.0 (rc2)

[Aldrin Piri]

+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: JIRA Ticket Help Needed

[Aldrin Piri]

Hi Alex,

You should be good to go!  Please let us know if you have any questions or
issues.

--aldrin

On Thu, Jan 31, 2019 at 11:47 AM Alex Aversa  wrote:

> Thanks!. Yeah, the "aaversa" would be the one to use.
>
> Take care,
>
> --Alex
>
>
>
> On Thu, Jan 31, 2019 at 9:35 AM Aldrin Piri  wrote:
>
> > Hi Alex,
> >
> > It looks like you have two accounts in JIRA, alexeaversa and aaversa.
> > Could you please let us know which one you wanted to use?
> >
> > On Thu, Jan 31, 2019 at 8:58 AM Alex Aversa 
> wrote:
> >
> > > Thanks Otto!
> > >
> > > -alex
> > >
> > > On Wed, Jan 30, 2019 at 5:03 PM Otto Fowler 
> > > wrote:
> > >
> > > > You can only be assigned tickets in jira if you are give a
> > `contributor`
> > > > role for that project in jira.
> > > > This must be done by a PMC member for that project.
> > > >
> > > >
> > > >
> > > > On January 30, 2019 at 16:59:17, Alex Aversa (alexeave...@gmail.com)
> > > > wrote:
> > > >
> > > > Hello,
> > > >
> > > > I had created a ticket in JIRA and it appears I am unable to assign
> the
> > > > ticket to myself and set the ticket status to "In Progress".
> > > >
> > > > https://issues.apache.org/jira/browse/NIFI-5986
> > > >
> > > > Is there a step I may have missed in adding this ticket that would
> > allow
> > > me
> > > > to assign it to myself and update its status? My thanks in advance
> for
> > > any
> > > > assistance with this.
> > > >
> > > > Take care,
> > > >
> > > > Alex
> > > >
> > >
> >
>

Re: JIRA Ticket Help Needed

[Aldrin Piri]

Hi Alex,

It looks like you have two accounts in JIRA, alexeaversa and aaversa.
Could you please let us know which one you wanted to use?

On Thu, Jan 31, 2019 at 8:58 AM Alex Aversa  wrote:

> Thanks Otto!
>
> -alex
>
> On Wed, Jan 30, 2019 at 5:03 PM Otto Fowler 
> wrote:
>
> > You can only be assigned tickets in jira if you are give a `contributor`
> > role for that project in jira.
> > This must be done by a PMC member for that project.
> >
> >
> >
> > On January 30, 2019 at 16:59:17, Alex Aversa (alexeave...@gmail.com)
> > wrote:
> >
> > Hello,
> >
> > I had created a ticket in JIRA and it appears I am unable to assign the
> > ticket to myself and set the ticket status to "In Progress".
> >
> > https://issues.apache.org/jira/browse/NIFI-5986
> >
> > Is there a step I may have missed in adding this ticket that would allow
> me
> > to assign it to myself and update its status? My thanks in advance for
> any
> > assistance with this.
> >
> > Take care,
> >
> > Alex
> >
>

Re: [EXT] Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Ah, thanks for clarifying.

I am also not aware of such functionality on GitHub.  For me, the most
valuable feature is being able to better curate our old/stale issues
without empty commits and, if so desired, obviate the need for the "This
closes" phrasing.

In terms of my personal review processes, I don't see myself carrying out
many merges from the web itself given that I am typically on the command
line anyway doing builds and testing.

Not really an answer to your original question but I hope this better
illustrates the integration capabilities.

--aldrin

On Fri, Dec 14, 2018 at 5:10 PM Peter Wicks (pwicks) 
wrote:

> Aldrin,
>
> Your comments have left me confused. Yes, in the past, I would always `-s`
> to sign the commits and push them. But isn't the idea behind the improved
> GitHub integration is that now I can just go to the PR and tell GitHub to
> accept the PR after I've reviewed it. Thus the manual act of amending the
> commit and signing it does not happen. Does that mean there is no Sign Off
> happening to the commit?
>
> --Peter
>
> -Original Message-
> From: Aldrin Piri [mailto:aldrinp...@gmail.com]
> Sent: Friday, December 14, 2018 2:32 PM
> To: dev 
> Subject: Re: [EXT] Re: [DISCUSS] Early, voluntary relocation to GitBox
>
> That level of interoperability is not there and, from some quick
> searching, do not believe it to be something that is supported. [1]
>
> Not sure what is meant by sign-off being automated.  Personally, I use the
> -s flag when amending/pushing reviewed commits.
>
> [1]
>
> https://blogs.apache.org/infra/entry/improved_integration_between_apache_and
>
> On Fri, Dec 14, 2018 at 3:34 PM Peter Wicks (pwicks) 
> wrote:
>
> > Does closing a PR through GitHub close the JIRA ticket correctly? I'm
> > assuming sign-off is automated this way, but wasn't sure about this step.
> >
> > Thanks,
> >   Peter
> >
> > -Original Message-
> > From: Aldrin Piri [mailto:aldrinp...@gmail.com]
> > Sent: Friday, December 14, 2018 6:23 AM
> > To: dev 
> > Subject: [EXT] Re: [DISCUSS] Early, voluntary relocation to GitBox
> >
> > Some clarifying notes until I can get all the updates into place and
> > generate a new email.
> >
> > There are now two locations that are writable by committers for each
> > of our repositories.  The updated repository locations can be seen in
> > the Apache NiFi section of https://gitbox.apache.org/repos/asf.  NiFi,
> > for instance, is available at
> > https://gitbox.apache.org/repos/asf/nifi-site.git.  The web view of
> > the repository is located at
> > https://gitbox.apache.org/repos/asf?p=nifi-site.git.  Please note the
> > subtle distinction!
> >
> > If you are a contributor still on their way to committership or you
> > are committer content with the same functionality we had with our old
> > setup (git-wip), you will use the above listed locations.  You can
> > update your location by performing the following steps:
> >
> >- Go to the root of your source directory, we'll use nifi as an
> example
> >   - cd ${repo_home}/nifi
> >- Update your remote.  On a default checkout this will be origin, but
> >use the name that is pointing to the old git-wip location (you can
> view
> >these using git remote -v)
> >   - git remote set-url origin
> >   https://gitbox.apache.org/repos/asf/nifi.git
> >
> >
> > If you are a committer and interested in making use of the tighter
> > GitHub integration, there are a few steps needed to enable this
> > described at https://gitbox.apache.org/setup/.  Please follow those
> > and give some time to allow the background processes sync.
> > Successfully completing them should result in the email from GitHub on
> > behalf of Gitbox I mentioned previously.
> >
> > Again, look for a bit more polished set of instructions in the next
> > hour or so but feel free to add any questions here in the interim if
> > it is holding you up.
> >
> >
> >
> > On Fri, Dec 14, 2018 at 7:35 AM Aldrin Piri 
> wrote:
> >
> > > Hey all,
> > >
> > > Just a quick note that migration has completed.  I'll be gathering
> > > up information shortly and sending out another, separate email to
> > > the community with any needed changes and will work to update our
> > > docs appropriately.
> > >
> > > Committers, you should have received an email regarding you addition
> > > to the nifi group on GitHub.
> > >
> > > --aldrin
> > >
> > > On Thu, D

Re: [EXT] Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

That level of interoperability is not there and, from some quick searching,
do not believe it to be something that is supported. [1]

Not sure what is meant by sign-off being automated.  Personally, I use the
-s flag when amending/pushing reviewed commits.

[1]
https://blogs.apache.org/infra/entry/improved_integration_between_apache_and

On Fri, Dec 14, 2018 at 3:34 PM Peter Wicks (pwicks) 
wrote:

> Does closing a PR through GitHub close the JIRA ticket correctly? I'm
> assuming sign-off is automated this way, but wasn't sure about this step.
>
> Thanks,
>   Peter
>
> -Original Message-
> From: Aldrin Piri [mailto:aldrinp...@gmail.com]
> Sent: Friday, December 14, 2018 6:23 AM
> To: dev 
> Subject: [EXT] Re: [DISCUSS] Early, voluntary relocation to GitBox
>
> Some clarifying notes until I can get all the updates into place and
> generate a new email.
>
> There are now two locations that are writable by committers for each of
> our repositories.  The updated repository locations can be seen in the
> Apache NiFi section of https://gitbox.apache.org/repos/asf.  NiFi, for
> instance, is available at
> https://gitbox.apache.org/repos/asf/nifi-site.git.  The web view of the
> repository is located at
> https://gitbox.apache.org/repos/asf?p=nifi-site.git.  Please note the
> subtle distinction!
>
> If you are a contributor still on their way to committership or you are
> committer content with the same functionality we had with our old setup
> (git-wip), you will use the above listed locations.  You can update your
> location by performing the following steps:
>
>- Go to the root of your source directory, we'll use nifi as an example
>   - cd ${repo_home}/nifi
>- Update your remote.  On a default checkout this will be origin, but
>use the name that is pointing to the old git-wip location (you can view
>these using git remote -v)
>   - git remote set-url origin
>   https://gitbox.apache.org/repos/asf/nifi.git
>
>
> If you are a committer and interested in making use of the tighter GitHub
> integration, there are a few steps needed to enable this described at
> https://gitbox.apache.org/setup/.  Please follow those and give some time
> to allow the background processes sync.  Successfully completing them
> should result in the email from GitHub on behalf of Gitbox I mentioned
> previously.
>
> Again, look for a bit more polished set of instructions in the next hour
> or so but feel free to add any questions here in the interim if it is
> holding you up.
>
>
>
> On Fri, Dec 14, 2018 at 7:35 AM Aldrin Piri  wrote:
>
> > Hey all,
> >
> > Just a quick note that migration has completed.  I'll be gathering up
> > information shortly and sending out another, separate email to the
> > community with any needed changes and will work to update our docs
> > appropriately.
> >
> > Committers, you should have received an email regarding you addition
> > to the nifi group on GitHub.
> >
> > --aldrin
> >
> > On Thu, Dec 13, 2018 at 1:20 PM Aldrin Piri 
> wrote:
> >
> >> Hey folks,
> >>
> >> The JIRA ticket has been submitted [1].  I will keep this thread
> >> updated as things progress and then generate a separate "helper"
> >> email for instructions/any updates that may be needed upon completion.
> >>
> >> [1] https://issues.apache.org/jira/browse/INFRA-17419
> >>
> >> On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard <
> >> pierre.villard...@gmail.com> wrote:
> >>
> >>> +1 as well, should ease the contribution workflow.
> >>> Thanks for volunteering Aldrin.
> >>>
> >>> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath
> >>>  a écrit :
> >>>
> >>> > +1
> >>> >
> >>> > On 10/12/2018, 15:22, "Michael Moser"  wrote:
> >>> >
> >>> > +1 from me, sounds great.
> >>> >
> >>> >
> >>> > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda
> >>> > 
> >>> > wrote:
> >>> >
> >>> > > +1 (for being the guinea pig __ )
> >>> > >
> >>> > > On 09/12/2018, 04:01, "Aldrin Piri" 
> >>> wrote:
> >>> > >
> >>> > > Thanks to those of you that responded.
> >>> > >
> >>> > > I think my tentative plan is to give this a few more days
> to
> >>> see
> >>> > if
> >>> > > th

Gitbox migration completed - What you need to do

[Aldrin Piri]

(quick note:  a markdown formatted version of this content is available at
[3])

All,

There was a flurry of messages as we sought to get some quick details out
about our migration to the ASF Gitbox system and I wanted to take this
message to consolidate those items into a comprehensive and less hastily
composed message.

There are a few different paths to consider and I will try to enumerate
those with the associated steps, so please choose your own adventure.
Please note that this change does affect ALL repositories in the NiFi
community and all references to NiFi refer to our efforts as a whole.

You have one or more repositories checked out. These repositories are
either from GitHub (in the case of NiFi, https://github.com/apache/nifi) or
git-wip (in the case of NiFi,
http://git-wip-us.apache.org/repos/asf/nifi.git). Each of the repositories
will need to be handled based on your role in the community and desired
functionality.
I
am an Apache NiFi contributor

   -

   *GitHub*: There are no actions required from you. You can continue to
   make use of the workflow already in place.
   -

   *git-wip*: You will need to update your remote to point to the new
   gitbox location. This can be accomplished via git remote set-url origin
   https://gitbox.apache.org/repos/asf/nifi.git

I
am an Apache NiFi committer and want to keep the same workflow with the
git-wip repositories

The key distinction is that the ASF Gitbox service considers both GitHub
and Gitbox repos as writable repositories. This is in contrast to before
the migration where GitHub was strictly a mirror of the git-wip
repositories.

   -

   *git-wip*: You will need to update your remote to point to the new
   gitbox location. This can be accomplished via git remote set-url origin
   https://gitbox.apache.org/repos/asf/nifi.git
   -

   *GitHub*: No changes are needed, but you will not be able to push to the
   repository.

I
am an Apache NiFi committer and would like access to the GitHub
functionality (Manually closing PRs, pushing to the GitHub repository
directly)

   -

   *git-wip* (Optional): You will need to update your remote to point to
   the new gitbox location. This can be accomplished via git remote set-url
   origin https://gitbox.apache.org/repos/asf/nifi.git
   -

   *GitHub*: You will need to


   1. link your Apache account to GitHub via https://id.apache.org/
   2. enable 2-Factor Authentication on GitHub for the account you wish to
   link at https://github.com/settings/security
   3. link your Apache & GitHub accounts to the GitBox service at
   https://gitbox.apache.org/setup/

*NOTE:* There are automated, periodic tasks that perform these
synchronizations. Give up to 30 minutes after completing each step should
you get stuck through the process before trying again.

   1. You should receive emails inviting you to various teams on GitHub.
   nifi-committers is the team needed for access to our repositories on
   GitHub
   2. You now have push access to the GitHub repositories in NiFi. You can
   choose to maintain the https:// url for the repositories, or, should you
   wish to leverage an existing GitHub ssh-key, you can update your remote for
   any repository via:

git remote set-url origin https://gitbox.apache.org/repos/asf/nifi.git

You can get the narrative of one committer setting this up and used as the
reference for the above list [1].

For more detail and background about GitBox, check out [2].

[1]
https://lists.apache.org/thread.html/e8c31b993eea119adcd7888f6669d2961bf6dd82184b0823a34e45a6@%3Cdev.nifi.apache.org%3E
[2] https://gitbox.apache.org/ [3] All,

There was a flurry of messages as we sought to get some quick details out
about our migration to the ASF Gitbox system and I wanted to take this
message to consolidate those items into a comprehensive and less hastily
composed message.

There are a few different paths to consider and I will try to enumerate
those with the associated steps, so please choose your own adventure.
Please note that this change does affect ALL repositories in the NiFi
community and all references to NiFi refer to our efforts as a whole.

You have one or more repositories checked out. These repositories are
either from GitHub (in the case of NiFi, https://github.com/apache/nifi) or
git-wip (in the case of NiFi,
http://git-wip-us.apache.org/repos/asf/nifi.git). Each of the repositories
will need to be handled based on your role in the community and desired
functionality.

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Hi Raymond,

Thanks for calling that out.  I am in the process of updating/deploying the
site as well as a final email with all the details but will be sure to
cover those links.

Thanks!
--aldrin

On Fri, Dec 14, 2018 at 10:37 AM ski n  wrote:

> Maybe good to check the link on the NiFi website (Development --> Source).
> It still points out to "https://git-wip-us.apache.org/repos/asf?p=nifi.git
> "
>
> Raymond
>
> Op vr 14 dec. 2018 om 15:13 schreef Aldrin Piri :
>
> > And in my frenzied typing, I made use of nifi-site's locations instead of
> > NiFi.
> >
> > NiFi is available at Gitbox for checkout at
> > https://gitbox.apache.org/repos/asf/nifi.git with its web view at
> > https://gitbox.apache.org/repos/asf?p=nifi.git
> >
> > On Fri, Dec 14, 2018 at 8:23 AM Aldrin Piri 
> wrote:
> >
> > > Some clarifying notes until I can get all the updates into place and
> > > generate a new email.
> > >
> > > There are now two locations that are writable by committers for each of
> > > our repositories.  The updated repository locations can be seen in the
> > > Apache NiFi section of https://gitbox.apache.org/repos/asf.  NiFi, for
> > > instance, is available at
> > > https://gitbox.apache.org/repos/asf/nifi-site.git.  The web view of
> the
> > > repository is located at
> > > https://gitbox.apache.org/repos/asf?p=nifi-site.git.  Please note the
> > > subtle distinction!
> > >
> > > If you are a contributor still on their way to committership or you are
> > > committer content with the same functionality we had with our old setup
> > > (git-wip), you will use the above listed locations.  You can update
> your
> > > location by performing the following steps:
> > >
> > >- Go to the root of your source directory, we'll use nifi as an
> > example
> > >   - cd ${repo_home}/nifi
> > >- Update your remote.  On a default checkout this will be origin,
> but
> > >use the name that is pointing to the old git-wip location (you can
> > view
> > >these using git remote -v)
> > >   - git remote set-url origin
> > >   https://gitbox.apache.org/repos/asf/nifi.git
> > >
> > >
> > > If you are a committer and interested in making use of the tighter
> GitHub
> > > integration, there are a few steps needed to enable this described at
> > > https://gitbox.apache.org/setup/.  Please follow those and give some
> > time
> > > to allow the background processes sync.  Successfully completing them
> > > should result in the email from GitHub on behalf of Gitbox I mentioned
> > > previously.
> > >
> > > Again, look for a bit more polished set of instructions in the next
> hour
> > > or so but feel free to add any questions here in the interim if it is
> > > holding you up.
> > >
> > >
> > >
> > > On Fri, Dec 14, 2018 at 7:35 AM Aldrin Piri 
> > wrote:
> > >
> > >> Hey all,
> > >>
> > >> Just a quick note that migration has completed.  I'll be gathering up
> > >> information shortly and sending out another, separate email to the
> > >> community with any needed changes and will work to update our docs
> > >> appropriately.
> > >>
> > >> Committers, you should have received an email regarding you addition
> to
> > >> the nifi group on GitHub.
> > >>
> > >> --aldrin
> > >>
> > >> On Thu, Dec 13, 2018 at 1:20 PM Aldrin Piri 
> > wrote:
> > >>
> > >>> Hey folks,
> > >>>
> > >>> The JIRA ticket has been submitted [1].  I will keep this thread
> > updated
> > >>> as things progress and then generate a separate "helper" email for
> > >>> instructions/any updates that may be needed upon completion.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/INFRA-17419
> > >>>
> > >>> On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard <
> > >>> pierre.villard...@gmail.com> wrote:
> > >>>
> > >>>> +1 as well, should ease the contribution workflow.
> > >>>> Thanks for volunteering Aldrin.
> > >>>>
> > >>>> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath <
> > lhorv...@hortonworks.com>
> > >>>> a
> > >>>> écrit :
> > >>>>
> >

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

And in my frenzied typing, I made use of nifi-site's locations instead of
NiFi.

NiFi is available at Gitbox for checkout at
https://gitbox.apache.org/repos/asf/nifi.git with its web view at
https://gitbox.apache.org/repos/asf?p=nifi.git

On Fri, Dec 14, 2018 at 8:23 AM Aldrin Piri  wrote:

> Some clarifying notes until I can get all the updates into place and
> generate a new email.
>
> There are now two locations that are writable by committers for each of
> our repositories.  The updated repository locations can be seen in the
> Apache NiFi section of https://gitbox.apache.org/repos/asf.  NiFi, for
> instance, is available at
> https://gitbox.apache.org/repos/asf/nifi-site.git.  The web view of the
> repository is located at
> https://gitbox.apache.org/repos/asf?p=nifi-site.git.  Please note the
> subtle distinction!
>
> If you are a contributor still on their way to committership or you are
> committer content with the same functionality we had with our old setup
> (git-wip), you will use the above listed locations.  You can update your
> location by performing the following steps:
>
>- Go to the root of your source directory, we'll use nifi as an example
>   - cd ${repo_home}/nifi
>- Update your remote.  On a default checkout this will be origin, but
>use the name that is pointing to the old git-wip location (you can view
>these using git remote -v)
>   - git remote set-url origin
>   https://gitbox.apache.org/repos/asf/nifi.git
>
>
> If you are a committer and interested in making use of the tighter GitHub
> integration, there are a few steps needed to enable this described at
> https://gitbox.apache.org/setup/.  Please follow those and give some time
> to allow the background processes sync.  Successfully completing them
> should result in the email from GitHub on behalf of Gitbox I mentioned
> previously.
>
> Again, look for a bit more polished set of instructions in the next hour
> or so but feel free to add any questions here in the interim if it is
> holding you up.
>
>
>
> On Fri, Dec 14, 2018 at 7:35 AM Aldrin Piri  wrote:
>
>> Hey all,
>>
>> Just a quick note that migration has completed.  I'll be gathering up
>> information shortly and sending out another, separate email to the
>> community with any needed changes and will work to update our docs
>> appropriately.
>>
>> Committers, you should have received an email regarding you addition to
>> the nifi group on GitHub.
>>
>> --aldrin
>>
>> On Thu, Dec 13, 2018 at 1:20 PM Aldrin Piri  wrote:
>>
>>> Hey folks,
>>>
>>> The JIRA ticket has been submitted [1].  I will keep this thread updated
>>> as things progress and then generate a separate "helper" email for
>>> instructions/any updates that may be needed upon completion.
>>>
>>> [1] https://issues.apache.org/jira/browse/INFRA-17419
>>>
>>> On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard <
>>> pierre.villard...@gmail.com> wrote:
>>>
>>>> +1 as well, should ease the contribution workflow.
>>>> Thanks for volunteering Aldrin.
>>>>
>>>> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath 
>>>> a
>>>> écrit :
>>>>
>>>> > +1
>>>> >
>>>> > On 10/12/2018, 15:22, "Michael Moser"  wrote:
>>>> >
>>>> > +1 from me, sounds great.
>>>> >
>>>> >
>>>> > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda >>> >
>>>> > wrote:
>>>> >
>>>> > > +1 (for being the guinea pig __ )
>>>> > >
>>>> > > On 09/12/2018, 04:01, "Aldrin Piri" 
>>>> wrote:
>>>> > >
>>>> > > Thanks to those of you that responded.
>>>> > >
>>>> > > I think my tentative plan is to give this a few more days
>>>> to see
>>>> > if
>>>> > > there
>>>> > > are any strong objections.  Otherwise, I'll look to file the
>>>> > ticket
>>>> > > around
>>>> > > midweek and then look to begin the process toward the end of
>>>> > next week
>>>> > > to
>>>> > > hopefully minimize disruptions.  Thanks again!
>>>> > >
>>>> > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc >>&

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Some clarifying notes until I can get all the updates into place and
generate a new email.

There are now two locations that are writable by committers for each of our
repositories.  The updated repository locations can be seen in the Apache
NiFi section of https://gitbox.apache.org/repos/asf.  NiFi, for instance,
is available at https://gitbox.apache.org/repos/asf/nifi-site.git.  The web
view of the repository is located at
https://gitbox.apache.org/repos/asf?p=nifi-site.git.  Please note the
subtle distinction!

If you are a contributor still on their way to committership or you are
committer content with the same functionality we had with our old setup
(git-wip), you will use the above listed locations.  You can update your
location by performing the following steps:

   - Go to the root of your source directory, we'll use nifi as an example
  - cd ${repo_home}/nifi
   - Update your remote.  On a default checkout this will be origin, but
   use the name that is pointing to the old git-wip location (you can view
   these using git remote -v)
  - git remote set-url origin
  https://gitbox.apache.org/repos/asf/nifi.git


If you are a committer and interested in making use of the tighter GitHub
integration, there are a few steps needed to enable this described at
https://gitbox.apache.org/setup/.  Please follow those and give some time
to allow the background processes sync.  Successfully completing them
should result in the email from GitHub on behalf of Gitbox I mentioned
previously.

Again, look for a bit more polished set of instructions in the next hour or
so but feel free to add any questions here in the interim if it is holding
you up.



On Fri, Dec 14, 2018 at 7:35 AM Aldrin Piri  wrote:

> Hey all,
>
> Just a quick note that migration has completed.  I'll be gathering up
> information shortly and sending out another, separate email to the
> community with any needed changes and will work to update our docs
> appropriately.
>
> Committers, you should have received an email regarding you addition to
> the nifi group on GitHub.
>
> --aldrin
>
> On Thu, Dec 13, 2018 at 1:20 PM Aldrin Piri  wrote:
>
>> Hey folks,
>>
>> The JIRA ticket has been submitted [1].  I will keep this thread updated
>> as things progress and then generate a separate "helper" email for
>> instructions/any updates that may be needed upon completion.
>>
>> [1] https://issues.apache.org/jira/browse/INFRA-17419
>>
>> On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard <
>> pierre.villard...@gmail.com> wrote:
>>
>>> +1 as well, should ease the contribution workflow.
>>> Thanks for volunteering Aldrin.
>>>
>>> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath 
>>> a
>>> écrit :
>>>
>>> > +1
>>> >
>>> > On 10/12/2018, 15:22, "Michael Moser"  wrote:
>>> >
>>> > +1 from me, sounds great.
>>> >
>>> >
>>> > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda 
>>> > wrote:
>>> >
>>> > > +1 (for being the guinea pig __ )
>>> > >
>>> > > On 09/12/2018, 04:01, "Aldrin Piri" 
>>> wrote:
>>> > >
>>> > > Thanks to those of you that responded.
>>> > >
>>> > > I think my tentative plan is to give this a few more days to
>>> see
>>> > if
>>> > > there
>>> > > are any strong objections.  Otherwise, I'll look to file the
>>> > ticket
>>> > > around
>>> > > midweek and then look to begin the process toward the end of
>>> > next week
>>> > > to
>>> > > hopefully minimize disruptions.  Thanks again!
>>> > >
>>> > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc 
>>> > wrote:
>>> > >
>>> > > > +1, sounds like a great idea
>>> > > >
>>> > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen <
>>> > mikerthom...@gmail.com>
>>> > > > wrote:
>>> > > >
>>> > > > > +1
>>> > > > >
>>> > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna <
>>> > > sivaprasanna...@gmail.com>
>>> > > > > wrote:
>>> > > > >
>>> > > > > > +1 (non-binding)
>>> > > > > >
>>> > &

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Hey all,

Just a quick note that migration has completed.  I'll be gathering up
information shortly and sending out another, separate email to the
community with any needed changes and will work to update our docs
appropriately.

Committers, you should have received an email regarding you addition to the
nifi group on GitHub.

--aldrin

On Thu, Dec 13, 2018 at 1:20 PM Aldrin Piri  wrote:

> Hey folks,
>
> The JIRA ticket has been submitted [1].  I will keep this thread updated
> as things progress and then generate a separate "helper" email for
> instructions/any updates that may be needed upon completion.
>
> [1] https://issues.apache.org/jira/browse/INFRA-17419
>
> On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard <
> pierre.villard...@gmail.com> wrote:
>
>> +1 as well, should ease the contribution workflow.
>> Thanks for volunteering Aldrin.
>>
>> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath  a
>> écrit :
>>
>> > +1
>> >
>> > On 10/12/2018, 15:22, "Michael Moser"  wrote:
>> >
>> > +1 from me, sounds great.
>> >
>> >
>> > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda 
>> > wrote:
>> >
>> > > +1 (for being the guinea pig __ )
>> > >
>> > > On 09/12/2018, 04:01, "Aldrin Piri"  wrote:
>> > >
>> > > Thanks to those of you that responded.
>> > >
>> > > I think my tentative plan is to give this a few more days to
>> see
>> > if
>> > > there
>> > > are any strong objections.  Otherwise, I'll look to file the
>> > ticket
>> > > around
>> > > midweek and then look to begin the process toward the end of
>> > next week
>> > > to
>> > > hopefully minimize disruptions.  Thanks again!
>> > >
>> > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc 
>> > wrote:
>> > >
>> > > > +1, sounds like a great idea
>> > > >
>> > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen <
>> > mikerthom...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > +1
>> > > > >
>> > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna <
>> > > sivaprasanna...@gmail.com>
>> > > > > wrote:
>> > > > >
>> > > > > > +1 (non-binding)
>> > > > > >
>> > > > > > I’m in. Thanks for doing it, Aldrin.
>> > > > > >
>> > > > > >
>> > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing <
>> > jvw...@gmail.com>
>> > > wrote:
>> > > > > >
>> >     > > > > > +1, thanks for volunteering.
>> > > > > > >
>> > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran <
>> > > kdoran.apa...@gmail.com>
>> > > > > wrote:
>> > > > > > > >
>> > > > > > > > +1
>> > > > > > > >
>> > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" <
>> > alopre...@apache.org>
>> > > wrote:
>> > > > > > > >
>> > > > > > > >+1.
>> > > > > > > >
>> > > > > > > >Andy LoPresto
>> > > > > > > >alopre...@apache.org
>> > > > > > > >alopresto.apa...@gmail.com
>> > > > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE
>> > 3C6E F65B
>> > > 2F7D
>> > > > > EF69
>> > > > > > > >
>> > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri <
>> > > aldrinp...@gmail.com>
>> > > > > > wrote:
>> > > > > > > >>
>> > > > > > > >> Hey folks,
>> > > > > > > >>
>> > > > > > > >> Danie

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Hey folks,

The JIRA ticket has been submitted [1].  I will keep this thread updated as
things progress and then generate a separate "helper" email for
instructions/any updates that may be needed upon completion.

[1] https://issues.apache.org/jira/browse/INFRA-17419

On Mon, Dec 10, 2018 at 10:51 AM Pierre Villard 
wrote:

> +1 as well, should ease the contribution workflow.
> Thanks for volunteering Aldrin.
>
> Le lun. 10 déc. 2018 à 16:41, Laszlo Horvath  a
> écrit :
>
> > +1
> >
> > On 10/12/2018, 15:22, "Michael Moser"  wrote:
> >
> > +1 from me, sounds great.
> >
> >
> > On Mon, Dec 10, 2018 at 4:07 AM Arpad Boda 
> > wrote:
> >
> > > +1 (for being the guinea pig __ )
> > >
> > > On 09/12/2018, 04:01, "Aldrin Piri"  wrote:
> > >
> > > Thanks to those of you that responded.
> > >
> > > I think my tentative plan is to give this a few more days to
> see
> > if
> > > there
> > > are any strong objections.  Otherwise, I'll look to file the
> > ticket
> > > around
> > > midweek and then look to begin the process toward the end of
> > next week
> > > to
> > > hopefully minimize disruptions.  Thanks again!
> > >
> > > On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc 
> > wrote:
> > >
> > > > +1, sounds like a great idea
> > > >
> > > > On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen <
> > mikerthom...@gmail.com>
> > > > wrote:
> > > >
> > > > > +1
> > > > >
> > > > > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna <
> > > sivaprasanna...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > I’m in. Thanks for doing it, Aldrin.
> > > > > >
> > > > > >
> > > > > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing <
> > jvw...@gmail.com>
> > > wrote:
> > > > > >
> > > > > > > +1, thanks for volunteering.
> > > > > > >
> > > > > > > > On Dec 7, 2018, at 13:39, Kevin Doran <
> >     > kdoran.apa...@gmail.com>
> > > > > wrote:
> > > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > On 12/7/18, 15:17, "Andy LoPresto" <
> > alopre...@apache.org>
> > > wrote:
> > > > > > > >
> > > > > > > >+1.
> > > > > > > >
> > > > > > > >Andy LoPresto
> > > > > > > >alopre...@apache.org
> > > > > > > >alopresto.apa...@gmail.com
> > > > > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE
> > 3C6E F65B
> > > 2F7D
> > > > > EF69
> > > > > > > >
> > > > > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri <
> > > aldrinp...@gmail.com>
> > > > > > wrote:
> > > > > > > >>
> > > > > > > >> Hey folks,
> > > > > > > >>
> > > > > > > >> Daniel Gruno sent an email to the dev list about the
> > > deprecation
> > > > of
> > > > > > our
> > > > > > > >> git-wip repositories [1] (these are the canonical
> > repos that
> > > > > > committers
> > > > > > > >> push changes to and are currently mirrored to
> GitHub)
> > and
> > > > > > transitioning
> > > > > > > to
> > > > > > > >> GitBox [2].
> > > > > > > >>
> > > > > > > >> As highlighted in that email, this will not be an
> > optional
> > > change,
> > > > > > only

Re: Apache NiFi

[Aldrin Piri]

Based on the versions that worked/didn't work, I am assuming this concerns
the host header protections that was covered in NIFI-4761 and then made
configurable to our Docker image in NIFI-4788.  What changed is detailed in
the admin guide toward the bottom of the Proxy Configuration section [3].

If this doesn't quite seem to coincide with what you are experiencing, more
information (inclusive of compose file, if possible) would be great.

[1] https://issues.apache.org/jira/browse/NIFI-4761
[2] https://issues.apache.org/jira/browse/NIFI-4788
[3]
https://github.com/mcgilman/nifi/blob/acb19a91fc7908e10dbc2b4364daa1657fc7657b/nifi-docs/src/main/asciidoc/administration-guide.adoc#proxy-configuration

On Wed, Dec 12, 2018 at 1:09 PM Mike Thomsen  wrote:

> Samir,
>
> Can you be more specific, preferably posting some logs?
>
> Thanks,
>
> Mike
>
> On Wed, Dec 12, 2018 at 12:13 PM Zaciragic, Samir * <
> samir.zacira...@fda.hhs.gov> wrote:
>
> > Hello,
> >
> > We are FDA docker support team trying to assist internal teams to onboard
> > their applications. We were able to pull latest apache NiFi (1.8.0) and
> run
> > container manually, but we faced an issue to use docker-compose to start
> > the service. One of our teammates found that older version of apache Nifi
> > (1.4.0) works, but none of newer versions due to the fact that newer
> > version have some security features that prevent docker service to run
> > properly.
> >
> > Is there some particular setup we are missing, that would help run the
> > service with newer version? Any assistance would be greatly appreciated.
> >
> > Thank you!
> >
>

Re: Apache NiFi contributor access

[Aldrin Piri]

Hi Satwik,

I've added you to the list of contributors.   Please let us know if you
have any issues.  We look forward to your contributions and working with
you!

--aldrin

On Tue, Dec 11, 2018 at 2:29 AM S Bhandiwad, Satwik (Nokia - IN/Bangalore) <
satwik.s_bhandi...@nokia.com> wrote:

> Hi,
>
> I would like to get contributor access to Apache Nifi on JIRA. Can you
> please add me to contributor list? My username is SatwikB.
>
> Thanks,
> Satwik
>

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Thanks to those of you that responded.

I think my tentative plan is to give this a few more days to see if there
are any strong objections.  Otherwise, I'll look to file the ticket around
midweek and then look to begin the process toward the end of next week to
hopefully minimize disruptions.  Thanks again!

On Sat, Dec 8, 2018 at 12:09 PM Tony Kurc  wrote:

> +1, sounds like a great idea
>
> On Sat, Dec 8, 2018 at 7:44 AM Mike Thomsen 
> wrote:
>
> > +1
> >
> > On Fri, Dec 7, 2018 at 9:08 PM Sivaprasanna 
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > I’m in. Thanks for doing it, Aldrin.
> > >
> > >
> > > On Sat, 8 Dec 2018 at 7:32 AM, James Wing  wrote:
> > >
> > > > +1, thanks for volunteering.
> > > >
> > > > > On Dec 7, 2018, at 13:39, Kevin Doran 
> > wrote:
> > > > >
> > > > > +1
> > > > >
> > > > > On 12/7/18, 15:17, "Andy LoPresto"  wrote:
> > > > >
> > > > >    +1.
> > > > >
> > > > >Andy LoPresto
> > > > >alopre...@apache.org
> > > > >alopresto.apa...@gmail.com
> > > > >PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D
> > EF69
> > > > >
> > > > >> On Dec 7, 2018, at 11:11 AM, Aldrin Piri 
> > > wrote:
> > > > >>
> > > > >> Hey folks,
> > > > >>
> > > > >> Daniel Gruno sent an email to the dev list about the deprecation
> of
> > > our
> > > > >> git-wip repositories [1] (these are the canonical repos that
> > > committers
> > > > >> push changes to and are currently mirrored to GitHub) and
> > > transitioning
> > > > to
> > > > >> GitBox [2].
> > > > >>
> > > > >> As highlighted in that email, this will not be an optional change,
> > > only
> > > > in
> > > > >> when and how it happens.  There was a previous discussion over
> this
> > > > topic
> > > > >> [3] where it was generally well received but I think some of the
> > > > logistics
> > > > >> were never mapped out and thus the actual request to do so was
> never
> > > > >> executed.
> > > > >>
> > > > >> I am proposing we volunteer for the early relocation.  The process
> > > > looks to
> > > > >> be fairly straightforward and should ultimately only result in
> > > requiring
> > > > >> our contributors to add/replace their original git-wip based
> > remotes.
> > > > >>
> > > > >> If folks are in favor, I am happy to file the requisite INFRA
> ticket
> > > and
> > > > >> provide the associated communication/docs to the community to make
> > > this
> > > > >> happen.  Again, this is only about making the choice to perform
> this
> > > > >> migration now, in a coordinated manner, in lieu of the mass
> > migration
> > > > that
> > > > >> would happen later.
> > > > >>
> > > > >> From a project management standpoint, I think it is a nice bit of
> > > > >> functionality that lets us better curate our open PRs and, given
> my
> > > > prior
> > > > >> interest in the subject, would like to see it happen.
> > > > >>
> > > > >> --aldrin
> > > > >>
> > > > >> [1]
> > > > >>
> > > >
> > >
> >
> https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21aac390c4f627d8fb1f421b2@%3Cdev.nifi.apache.org%3E
> > > > >> [2] https://gitbox.apache.org/
> > > > >> [3]
> > > > >>
> > > >
> > >
> >
> https://lists.apache.org/thread.html/de5e103994f356b1b8a572410938eef44af8cb352210e35305c04bc9@%3Cdev.nifi.apache.org%3E
> > > > >
> > > > >
> > > >
> > >
> >
>

[DISCUSS] Early, voluntary relocation to GitBox

[Aldrin Piri]

Hey folks,

Daniel Gruno sent an email to the dev list about the deprecation of our
git-wip repositories [1] (these are the canonical repos that committers
push changes to and are currently mirrored to GitHub) and transitioning to
GitBox [2].

As highlighted in that email, this will not be an optional change, only in
when and how it happens.  There was a previous discussion over this topic
[3] where it was generally well received but I think some of the logistics
were never mapped out and thus the actual request to do so was never
executed.

I am proposing we volunteer for the early relocation.  The process looks to
be fairly straightforward and should ultimately only result in requiring
our contributors to add/replace their original git-wip based remotes.

If folks are in favor, I am happy to file the requisite INFRA ticket and
provide the associated communication/docs to the community to make this
happen.  Again, this is only about making the choice to perform this
migration now, in a coordinated manner, in lieu of the mass migration that
would happen later.

>From a project management standpoint, I think it is a nice bit of
functionality that lets us better curate our open PRs and, given my prior
interest in the subject, would like to see it happen.

--aldrin

[1]
https://lists.apache.org/thread.html/8247bb17671d6131b1d7a646b4c018b21aac390c4f627d8fb1f421b2@%3Cdev.nifi.apache.org%3E
[2] https://gitbox.apache.org/
[3]
https://lists.apache.org/thread.html/de5e103994f356b1b8a572410938eef44af8cb352210e35305c04bc9@%3Cdev.nifi.apache.org%3E

Re: How to fetch remote windows event logs with minifi agent and ConsumeWindowsEventLog processor

[Aldrin Piri]

Hello,

Did you add the windows-event-log nar to your MiNiFi distribution?  This is
not a bundle that is automatically included.  The log is creating a ghost
implementation as it cannot find a backing implementation for that
component coordinate.  This is likely the best approach but you will need
to augment the standard minifi distribution to also support this
functionality.

As far as your second approach, this is unlikely to be the result you are
looking for.  To the best of my knowledge, the evtx format is a format that
would not lend itself well to the appended log format TailFile is expecting.

On Thu, Nov 1, 2018 at 12:23 PM Jagan  wrote:

> Hi all...
>
> I am trying to fetch remote windows server event logs in two ways
> 1.by installing minifi agent on the remote server and then created a
> minifi
> config.yml with ConsumeWindowsEventLog processor and Remote process group
>
> after that I have started minifi agent where ConsumeWindowsEventLog
> processor able to read logs from windows event log but was not able to send
> them to Remote process group here messages are getting queued and not
> reaching Remote process group
>
> where I have seen following error in minifi agent logs
>
> 2018-10-31 21:02:36,690 WARN [main] org.apache.nifi.minifi.FlowEnricher
> Could not find any eligible bundles for
> org.apache.nifi.processors.windows.event.log.ConsumeWindowsEventLog.
> Automatic start of the flow cannot be guaranteed.
> 2018-10-31 21:02:41,011 WARN [main] o.a.n.c.StandardFlowSynchronizer Schema
> validation error parsing Flow Configuration at line 16, col 27:
> cvc-complex-type.2.4.a: Invalid content was found starting with element
> 'maxConcurrentTasks'. One of '{bundle}' is expected.
> 2018-10-31 21:02:41,489 ERROR [main]
> o.apache.nifi.controller.FlowController
> Could not create Processor of type
> org.apache.nifi.processors.windows.event.log.ConsumeWindowsEventLog for ID
> 2b67acce-9365-3433--; creating "Ghost" implementation
> org.apache.nifi.controller.exception.ProcessorInstantiationException:
> Unable
> to find bundle for coordinate default:unknown:unversioned at
>
> org.apache.nifi.controller.FlowController.instantiateProcessor(FlowController.java:1271)
>
> please suggest me how can I overcome this error...
> and the second method is
>
> 2..by installing minifi agent on the remote server and then created a
> minifi
> config.yml with tailfile processor and Remote process group
> here I am specifying the file  location of
> Application.evtx(C:\Windows\System32\winevt\Logs\Application.evtx
> )
>
> will this method work for fetching remote windows server event logs because
> when I try this I got no response from tail file processor
>
> and please suggest me if there are better ways to do this
>
> Thank you all...
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

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

[Aldrin Piri]

+1, binding

Comments
---
Hashes and signature correct
commit and source match
full build, tests and contrib-check all pass
simple running of some saved flows via registry looked good and functioned
as anticipated

On Tue, Oct 23, 2018 at 1:59 PM Matt Gilman  wrote:

> +1 Release this package as nifi-1.8.0
>
> Validated build, checksums, etc. Ran various deployment configurations and
> verified new capabilities.
>
> Thanks for RMing Jeff!
>
> Matt
>
> On Tue, Oct 23, 2018 at 1:56 AM 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

[Aldrin Piri]

+1, binding

comments:
verified hashes and signature
commit and source check out
build and tests were good
did some cursory testing with integration with registry and minifi, all
looked good


On Fri, Oct 19, 2018 at 11:21 AM Matt Burgess  wrote:

> +1 (binding), verified via release helper, ran full build with unit
> tests, tried various flows on a standalone instance.  Great work
> everyone! Thanks Jeff for RM'ing!
> On Wed, Oct 17, 2018 at 11: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: Command and Control Minifi - Documentation

[Aldrin Piri]

Hi Abhi,

There are a few components of the work that has gone around C2.  Part of
this is implemented with the C2 server which helps one aspect of instance
management through flow updates via a variety of providers outlined in its
docs [1].  These bits of functionality are fully formed and consumable now
and in use by a number of members of the community.  This is focused on the
issue of updating flows across a set of instances in a manner analogous to
the experience provided in NiFi.  Some of the key differences include the
notion of a more static design and deploy mechanism as well as the
introduction of an instance "class" which allows prescriptive deployments
for certain types of data collection and processing.  As an example, I may
have one class that deals with tailing log files on various application
servers and another class that acts as a bridge to forward data from a
legacy application that only transmits across raw socket.

Another aspect of C2 is the API described in the C2 Design Proposal [2].
The C++ work is leading the primary implementation of this with work being
done in parallel on the Java codebase to also support this functionality.
The C2 API dictates a set of actions that are to be handled by the agent
and the contract for each of those verbs.  There are several tickets
surrounding these efforts both in the MiNiFi Java [3] and C++ [4] that
would provide additional functionality and operations management.

[1] https://github.com/apache/nifi-minifi/blob/master/minifi-c2/README.md
[2]
https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal#C2DesignProposal-Protocols
[3] https://issues.apache.org/jira/browse/MINIFI
[4] https://issues.apache.org/jira/browse/MINIFICPP

On Sun, Sep 30, 2018 at 5:00 PM Abhinav Joshi 
wrote:

> Hi Nifi Team
>
> We want to make use of the Command and Control C2 mechanism to have a
> centralized control over the minifi agents. However I do not find any
> documentation on the net to start this . Can someone point to a link or
> provide some documentation on how to go about with getting the C2 mechanism
> working ?
>
> Thanks
>
> Abhi
>
>
> This communication, including any attachments, is confidential. If you are
> not the intended recipient, you should not read it - please contact me
> immediately, destroy it, and do not copy or use any part of this
> communication or disclose anything about it. Thank you. Please note that
> this communication does not designate an information system for the
> purposes of the Contract and Commercial Law Act 2017.
>
>

Re: [VOTE] Release Apache NiFi Registry 0.3.0

[Aldrin Piri]

+1, binding

comments
hashes and signature look good
build and tests were good
verified integration with NiFi and versioning of some process groups

On Mon, Sep 24, 2018 at 7:36 PM Marc Parisi  wrote:

> +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: Improve S2S to ease "star deployments"

[Aldrin Piri]

MQTT can function in its own right outside of Site to Site and MiNiFi could
support that using processors.

A bit of time ago, I made NIFI-1820 [1] which can be notionally summed up
as being "extend Site to Site with caveats depending on backing protocol."
Conceptually, I like what this could provide from a consistent
operator/user perspective and would allow Site to Site to be the prescribed
way of handling data transport between instances within the NiFi ecosystem
using the FlowFile format.  Implementation wise this certainly affects many
parts of the codebase and may additionally need a major release to be
feasible.

[1] https://issues.apache.org/jira/browse/NIFI-1820

On Mon, Sep 17, 2018 at 4:20 AM Pierre Villard 
wrote:

> Yeah I think the HTTP approach is fine for my use case where the number of
> "satellites" is limited.
>
> However, we can extend this discussion to the IoT use case where satellites
> are MiNiFi agents and where the number of agents is thousands or more. In
> that case the HTTP approach won't scale and I don't know if MQTT can be
> used for this kind of specific delivery (enriched data needs to go back to
> a specific agent). Curious to know how we could answer that requirement.
>
> Pierre
>
> Le lun. 17 sept. 2018 à 03:59, Joe Percivall  a
> écrit :
>
> > Echoing Mark's advice, we have a "star deployment" and use InvokeHttp
> with
> > EL to send requests back "out.
> >
> > For the addition of PUB/SUB to S2S, I'd be wary of scope creep. PUB/SUB
> has
> > entire Apache projects dedicated to getting it right.
> >
> > Joe
> >
> > On Sun, Sep 16, 2018 at 3:29 PM Ed B  wrote:
> >
> > > Pierre, Mark,
> > > Although I agree it is possible to work it around with HTTP
> > > (Post/Listen/Invoke), I still think that PUB/SUB for S2S (regardless it
> > is
> > > on the same cluster or different ones) worth discussion and
> > implementation.
> > > That would make implementation more natural and mature.
> > >
> > > Pierre, don't give up :) Let's discuss more on ideas and have a design.
> > > In addition, I believe that this idea should be combined with "Womhole
> > > connections"
> > >  >
> > > idea. So, that will give us full design for procedural development in
> > NIFI.
> > >
> > > Thoughts?
> > > Ed.
> > >
> > > On Sat, Sep 15, 2018 at 9:53 AM Pierre Villard <
> > > pierre.villard...@gmail.com>
> > > wrote:
> > >
> > > > Hi Mark,
> > > >
> > > > Thanks for the answer. You're right, I was going to use
> > > > ProcessSession.get(FlowFileFilter);
> > > > And I considered that I would set an expiration date on the flow file
> > in
> > > > case a standalone instance is not pulling data to ensure that the
> queue
> > > is
> > > > not filling up. But I didn't think about the data being swapped out
> > and,
> > > > you're right, we probably don't want to change that.
> > > >
> > > > The HTTP approach sounds indeed like a very good option for my use
> > case.
> > > > Thanks for mentioning it.
> > > >
> > > > Pierre
> > > >
> > > >
> > > >
> > > > Le sam. 15 sept. 2018 à 15:40, Mark Payne  a
> > > écrit :
> > > >
> > > > > Hey Pierre,
> > > > >
> > > > > I'm not sure that this is the best route to go down. There are a
> > couple
> > > > of
> > > > > problems that I think
> > > > > you will run into. The most important will be what happens when the
> > > data
> > > > > going to that Output Port
> > > > > queues up into a large queue? If a NiFi instance then requests
> data,
> > I
> > > > > presume that the Output Port
> > > > > would determine which FlowFiles to send by calling
> > > > > ProcessSession.get(FlowFileFilter);
> > > > > But currently, if I'm not mistaken, that method only iterates over
> > the
> > > > > data in the 'active' queue, not
> > > > > data that is swapped out. As a result, you could have the active
> > queue
> > > > > filled up with data for nodes
> > > > > that are not pulling, and that would prevent any node from pulling
> > > data.
> > > > >
> > > > > Even if we were to change it so that the get(FlowFileFilter) method
> > > runs
> > > > > through swapped out data,
> > > > > the expense of doing that would likely be cost-prohibitive for this
> > > > > approach, as the disk I/O to constantly
> > > > > scan the swap files would be too expensive. To make that approach
> > > > feasible
> > > > > you'd probably also have to
> > > > > change the Swap File format so that its "summary" also contains a
> > > mapping
> > > > > of S2S.host to count of FlowFile
> > > > > for that host. And this is already getting way beyond the scope I
> > think
> > > > of
> > > > > what you want to do here.
> > > > >
> > > > > Additionally, I feel like where this concept is heading is
> difficult
> > to
> > > > > explain and is designed for a rather
> > > > > specific use case, because it starts to make this into a sort of
> > > > > quasi-pub-sub mechanism but not a true pub/sub.
> > > > >
> > > > > Rather, I would propose that when the

Re: Request to assign jira tickets

[Aldrin Piri]

Hey there, Vijeta!

I've added you to the list of contributors so you should be all set.  You
may need to refresh your session but should otherwise be good to go.
Please let us know if you have any questions!

Looking forward to your contributions!

On Wed, Sep 12, 2018 at 11:42 AM Vijeta Hingorani <
vhingor...@boardreader.com> wrote:

> Hello All,
>
> I wanted to help contribute some documentation updates and would like to
> be able to assign tickets to myself in NiFi Jira.
>
> Apache JIRA ID : vijeta
> Email : vhingor...@boardreader.com
>
> Thank you,
> Vijeta
>

Re: Contrib Check Test Failures on master

[Aldrin Piri]

We've had some issues with this over time. Typically this is from an ISP
hijacking DNS and resolving an address that should note be resolved.  Does
the command listed in the test, host "bad data should be skipped"`, work in
your build environment?

On Sun, Aug 19, 2018 at 3:01 PM Jeremy Dyer  wrote:

> Team - I'm experiencing test failures on master. I was formulating a PR and
> noticed the failures when running -P contrib-check (this wasn't surprising
> as I often have them =) however on further inspection I noticed its
> happening on master as well. I see the failure of this test. Seems like
> something isn't quite right there and that message leads me to believe that
> my local machine should maybe even be skipping this test?
>
> [INFO] Running
> org.apache.nifi.cluster.firewall.impl.FileBasedClusterNodeFirewallTest
> [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.1
> s <<< FAILURE! - in
> org.apache.nifi.cluster.firewall.impl.FileBasedClusterNodeFirewallTest
> [ERROR]
>
> ensureBadDataWasIgnored(org.apache.nifi.cluster.firewall.impl.FileBasedClusterNodeFirewallTest)
> Time elapsed: 0.008 s  <<< FAILURE!
> java.lang.AssertionError: firewall treated our malformed data as a host. If
> `host "bad data should be skipped"` works locally, this test should have
> been skipped.
> at
>
> org.apache.nifi.cluster.firewall.impl.FileBasedClusterNodeFirewallTest.ensureBadDataWasIgnored(FileBasedClusterNodeFirewallTest.java:86)
>

Re: Version-Agnostic Paths in Docker?

[Aldrin Piri]

I'll scope it out. Thanks for taking an initial effort on it!

On Wed, Aug 8, 2018 at 8:29 AM Peter Wilcsinszky 
wrote:

> https://github.com/apache/nifi/pull/2940
>
> This is what I came up with, however not sure I covered your use case
> Aldrin. I tried to have a symlink with the name /opt/nifi/nifi-current to
> point to the original installation path, but the WORKDIR instruction
> resolves the link and we end up running NiFi in /opt/nifi/nifi-
> while the environment variables point to /opt/nifi/nifi-current which I
> would avoid.
> We can change the WORKDIR to be /opt/nifi and cd into nifi-current from the
> script, but that would be a breaking change I beleive for anyone using
> custom scripts and depending on the original working directory.
>
> What do you think?
>
> Cheers,
> Peter
>
> On Tue, Jul 31, 2018 at 5:22 PM Aldrin Piri  wrote:
>
> > I don't think there is an explicit reason why it was done that way,
> rather
> > this was the convention established with the way the artifacts were
> > imported into the image and the way the assembly is constructed.
> >
> > Typically, at least in how I personally use the image, I am making use of
> > volumes and am explicitly setting a version that is used throughout my
> > simple script.  This gives me the flexibilities I need in terms of
> upgrades
> > and the like.
> >
> > Having said all that, certainly in favor of the path suggested, it makes
> > sense and is a nice and easy usability win.  I would be sure to keep the
> > versioned approach for those folks who prefer that convention and then
> > additionally add a latest symlink.
> >
> > On Tue, Jul 31, 2018 at 2:10 AM Peter Wilcsinszky <
> > peterwilcsins...@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I was wondering about this too. We have the option to add a symlink
> which
> > > you just mentioned and I can do that if there are no argument against.
> > >
> > > Also you can use the env var, when you do things through scripting:
> > > docker run --rm -ti --entrypoint bash apache/nifi:1.7.0 -c "echo
> > > \$NIFI_HOME"
> > > /opt/nifi/nifi-1.7.0
> > >
> > > I'm not sure about the original reasons it was created this way. We may
> > > change to a version agnostic path with the next release and create a
> > > symlink with the version for backward compatibility.
> > >
> > > Peter
> > >
> > > On Tue, Jul 31, 2018 at 12:01 AM Jon Logan 
> wrote:
> > >
> > > > Hi,
> > > >
> > > > I was looking at utilizing the Docker distribution but was wondering
> if
> > > any
> > > > thought was given to making the paths version-agnostic? Specifically,
> > the
> > > > conf folder is in /opt/nifi/nifi-1.7.1/conf. This would mean any
> > > > modifications we would make in a container or RPM would be tied to
> > 1.7.1.
> > > >
> > > > I have seen other projects accomplish this with a symlink (ex.
> > > > /opt/nifi/latest -> opt/nifi/nifi-1.7.1), and think that approach
> might
> > > > work as well here?
> > > >
> > > > Is there a better approach?
> > > >
> > > >
> > > > Thanks!
> > > > Jon
> > > >
> > >
> >
>

Re: Version-Agnostic Paths in Docker?

[Aldrin Piri]

I don't think there is an explicit reason why it was done that way, rather
this was the convention established with the way the artifacts were
imported into the image and the way the assembly is constructed.

Typically, at least in how I personally use the image, I am making use of
volumes and am explicitly setting a version that is used throughout my
simple script.  This gives me the flexibilities I need in terms of upgrades
and the like.

Having said all that, certainly in favor of the path suggested, it makes
sense and is a nice and easy usability win.  I would be sure to keep the
versioned approach for those folks who prefer that convention and then
additionally add a latest symlink.

On Tue, Jul 31, 2018 at 2:10 AM Peter Wilcsinszky <
peterwilcsins...@gmail.com> wrote:

> Hi,
>
> I was wondering about this too. We have the option to add a symlink which
> you just mentioned and I can do that if there are no argument against.
>
> Also you can use the env var, when you do things through scripting:
> docker run --rm -ti --entrypoint bash apache/nifi:1.7.0 -c "echo
> \$NIFI_HOME"
> /opt/nifi/nifi-1.7.0
>
> I'm not sure about the original reasons it was created this way. We may
> change to a version agnostic path with the next release and create a
> symlink with the version for backward compatibility.
>
> Peter
>
> On Tue, Jul 31, 2018 at 12:01 AM Jon Logan  wrote:
>
> > Hi,
> >
> > I was looking at utilizing the Docker distribution but was wondering if
> any
> > thought was given to making the paths version-agnostic? Specifically, the
> > conf folder is in /opt/nifi/nifi-1.7.1/conf. This would mean any
> > modifications we would make in a container or RPM would be tied to 1.7.1.
> >
> > I have seen other projects accomplish this with a symlink (ex.
> > /opt/nifi/latest -> opt/nifi/nifi-1.7.1), and think that approach might
> > work as well here?
> >
> > Is there a better approach?
> >
> >
> > Thanks!
> > Jon
> >
>

Re: running nifi in windows server

[Aldrin Piri]

Hello,

Could you please share what version you are attempting to use?

On Mon, Jul 23, 2018 at 11:00 AM Vicent Sendra Server 
wrote:

> Hello,
>
>
>
> I’m trying to run minifi as a Windows service, in a Windows 2016 server.
>
> It is already installed, but when I try to start the service I receive the
> following error:
>
>
>
> 2018-07-23 07:22:22 Commons Daemon procrun stderr initialized
>
> java.lang.NoClassDefFoundError:
> org/apache/nifi/minifi/bootstrap/WindowsService
>
> Caused by: java.lang.ClassNotFoundException:
> org.apache.nifi.minifi.bootstrap.WindowsService
>
>at java.net.URLClassLoader.findClass(Unknown Source)
>
>at java.lang.ClassLoader.loadClass(Unknown Source)
>
>at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
>
>at java.lang.ClassLoader.loadClass(Unknown Source)
>
> Exception in thread "main"
>
>
>
> I found this solution on github:
>
>
> https://github.com/apache/nifi-minifi/tree/05ad9679c162dd3bf38632c7c81762ce3cd3de0e
>
>
>
> where I found the WindowsService.java class .
>
>
>
> How can I integrate the WindowsService.java into the main installation and
> solve the problem?
>
>
>
> Thanks in advance and kind regars,
>
>
>
> *Vicent Sendra*
>
> *Information Security, Risk & Compliance*
>
> *Senior Technical Security Specialist*
>
> *Business Process & Technology*
>
> E. vsendraser...@cokecce.com
>
> T. +34 93 496 6683
>
>
>
>
>
> Av. Països Catalans 32  www.ccep.com
>
> 08950 Esplugues de Llobregat
>
> Spain
>
>
>
>
>
> [image: http://www.cocacolaiberianpartners.com/logomail/logoccep.jpg]
>
>
>
>
>
>
>

Re: Contributor access to NiFi

[Aldrin Piri]

Ah drat.  Sorry about that, I accidentally got someone with first name Uday
instead of username Uday.  I had assigned NIFI-1184 to you in the
meantime.  Let us know if you run into further troubles, but username Uday (
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uday) is now in
contributors.

Sorry for the blunder.


On Sun, Jul 15, 2018 at 9:43 AM uday kale  wrote:

> Thanks Aldrin,
> I am working on NIFI-1184. I am unable to assign the issue to myself.
>
>
> On Sun, Jul 15, 2018 at 7:08 PM Aldrin Piri  wrote:
>
> > Hi Uday,
> >
> > I've added the requested username to the contributors list.  Let us know
> if
> > you have any issues and thanks for getting involved in the project!
> >
> > --aldrin
> >
> > On Sun, Jul 15, 2018 at 7:06 AM uday kale  wrote:
> >
> > > Hi,
> > >
> > > I would like to get contributors access to NiFi on Jira. My username is
> > > 'uday'.
> > >
> > > Regards,
> > > Uday
> > >
> >
>

Re: Contributor access to NiFi

[Aldrin Piri]

Hi Uday,

I've added the requested username to the contributors list.  Let us know if
you have any issues and thanks for getting involved in the project!

--aldrin

On Sun, Jul 15, 2018 at 7:06 AM uday kale  wrote:

> Hi,
>
> I would like to get contributors access to NiFi on Jira. My username is
> 'uday'.
>
> Regards,
> Uday
>

Re: [VOTE] Release Apache NiFi 1.7.1

[Aldrin Piri]

+1, binding

hashes and signature looked good
full build with contrib-check passed
L&N looked good
ran some simple flows
verified integration with registry
confirmed successful build of Docker artifacts

On Sat, Jul 14, 2018 at 12:06 PM Otto Fowler 
wrote:

> +1
> validated using rc-check script ( signed, hashed, commit matches, builds
> per guide, runs )
> Ran manual, validate help and version in about.
>
>
>
> On July 14, 2018 at 09:21:57, Pierre Villard (pierre.villard...@gmail.com)
> wrote:
>
> +1, binding
>
> Ran through release helper guide and confirmed fixes for wildcard
> certificates and threads interruption.
>
> Thanks for taking care of the RM duties Andy!
>
> Pierre
>
> 2018-07-14 1:17 GMT+02:00 Andy LoPresto :
>
> > Thanks for catching that Drew. I missed cherry picking the commit into
> the
> > release branch. I don’t think it rises to the level of canceling this
> > release, but I will note in the release notes that the ticket is not
> > included and add extra notes to the migration guidance.
> >
> > Andy LoPresto
> > alopre...@apache.org
> > alopresto.apa...@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> >
> > > On Jul 13, 2018, at 13:53, Andrew Lim 
> > wrote:
> > >
> > > +1 (non-binding)
> > >
> > > -Ran full clean install on OS X (10.11.6)
> > > -Tested integration with NiFi Registry (0.2.0)
> > > -Ran some basic flows; working as expected.
> > > -Reviewed documentation. Noticed that the doc added for wildcard
> > certificates was included in master but not 1.7.1 [1]
> > >
> > > Drew
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-5339
> > >
> > >> On Jul 12, 2018, at 4:59 PM, Andy LoPresto 
> > wrote:
> > >>
> > >> Hello,
> > >>
> > >> I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.7.1.
> > >>
> > >> The source zip, including signatures, digests, etc. can be found at:
> > >> https://repository.apache.org/content/repositories/orgapachenifi-1131
> > >>
> > >> The Git tag is nifi-1.7.1-RC1
> > >> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
> > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
> > >>
> > >> Checksums of nifi-1.7.1-source-release.zip:
> > >> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> > >> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9f
> > a0e6
> > >> SHA512: a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c
> > 0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
> > >>
> > >> 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
> > >>
> > >> 13 issues were closed/resolved for this release:
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12343647
> > >>
> > >> Release note highlights can be found here:
> > >> https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.7.1
> > >>
> > >> 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. Then please vote:
> > >>
> > >> [ ] +1 Release this package as nifi-1.7.1
> > >> [ ] +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: First Timer

[Aldrin Piri]

Hi Corey,

Glad that you are interested in contributing to NiFi.  If you open up PRs
against the main Github repository (https://github.com/apache/nifi/pulls)
that should be sufficient.

In terms of 1.8.0, there is not a specific timeline as to when that release
will be conducted.  Historically, that has been roughly approximately every
three months.  A member of the community did some number crunching on that
here
https://lists.apache.org/thread.html/34fb5d1956a09ef57332fe059fbf34cf8b451f08b2d06fdf0b002aba@%3Cdev.nifi.apache.org%3E.
The linked thread also highlights some of the high level motions of the
release process.

Please let us know if you have any additional questions.

As a side note, and part of the reason for the lack of responsiveness, it
appears Gmail (at least) flagged this message as spam because it could not
verify it coming from your listed domain.

On Sat, Jul 7, 2018 at 12:45 AM Corey Fritz  wrote:

> We piloted a project with NiFi here at Snag over the past year and are
> starting to promote wider adoption. There are a couple of minor
> enhancements we'd like to add wrt the Kafka processors. I entered a ticket
> for one (NIFI-5388) and there was already a ticket for the other
> (NIFI-5083). I'm planning to tackle both of these, just wondering who I
> should submit PRs to when I'm ready. Also curious on the timeframe for the
> next release (1.8.0), including the deadline for code to be merged.
>
> *Corey Fritz | Principal Engineer*
> corey.fr...@snag.co
> *office* | 866.227.0466
>
> The information in this communication is intended to be confidential to
> the individual(s) and/or Entity to whom it is addressed. It may contain
> information of a Privileged and/or Confidential nature, which is subject to
> Federal and/or State privacy regulations. In the event that you are not the
> intended recipient or the agent of the intended recipient, do not copy or
> use the information contained within this communication, or allow it to be
> read, copied or utilized in any manner, by any other person(s). Should this
> communication be received in error, please notify the sender immediately
> either by response e-mail or by phone, and permanently delete the original
> e-mail, attachment(s), and any copies. Any consent must be separately and
> expressly obtained in writing from an authorized representative of
> Snagajob, Inc. Any views expressed in this message are those of the
> individual sender, except where the message states otherwise. Please be
> aware that we monitor all e-mail communication,
>  access and data transfers through our networks.
>

Re: Status of nifi-docker

[Aldrin Piri]

We may be lacking in that department but it is via a profile. Give -Pdocker as 
part of your maven build and it should build off your current source. 

> On Jun 29, 2018, at 19:32, Mike Thomsen  wrote:
> 
> Is there any documentation on how to build the dockermaven one? It just
> generates a 7kb jar for me.
> 
> Thanks,
> 
> Mike
> 
>> On Fri, Jun 29, 2018 at 10:36 AM Jeremy Dyer  wrote:
>> 
>> Mike - Yes both of them are used. The dockerhub one is obviously pushed to
>> dockerhub (and built there hence the separate file) and the dockermaven one
>> is built locally for anyone who wishes to do so. I know I use the
>> dockermaven one all the time for development purposes
>> 
>> Thanks,
>> Jeremy Dyer
>> 
>> Thanks - Jeremy Dyer
>> 
>> From: Pierre Villard 
>> Sent: Friday, June 29, 2018 10:11:31 AM
>> To: dev
>> Subject: Re: Status of nifi-docker
>> 
>> Wrong copy/paste... thread with title Question on Docker module
>> <
>> https://mail-archives.apache.org/mod_mbox/nifi-dev/201806.mbox/ajax/%3CCAGvqHsdf5fNuC2mGwmGWZRjQ3_T5W_MqtyB9KY9k7JGpEaL8yQ%40mail.gmail.com%3E
>>> 
>> 
>> 
>> 2018-06-29 16:10 GMT+02:00 Pierre Villard :
>> 
>>> Hi Mike,
>>> 
>>> Have a look on this thread: https://mail-archives.apache.
>>> org/mod_mbox/nifi-dev/201806.mbox/browser
>>> 
>>> Pierre
>>> 
>>> 2018-06-29 15:59 GMT+02:00 Mike Thomsen :
>>> 
 We appear to have two copies of the Docker builds. One in dockerhub and
 one
 in dockermaven. Do we use both of them? I need to know so I can try to
 finish up a PR to expose ZK-based clustering w/ Docker.
 
 Thanks,
 
 Mike
 
>>> 
>>> 
>> 

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

[Aldrin Piri]

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, 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!
> > >
> >
>

Re: Need to be added to the Registry Jira project

[Aldrin Piri]

Mike,

I added mike.thomsen.  Let me know if it's not working.

On Fri, Jun 29, 2018 at 9:49 AM Mike Thomsen  wrote:

> Can someone set me up as a contributor?
>
> Thanks,
>
> Mike
>

Re: [DISCUSS] Tar + Gzip vs. Zip

[Aldrin Piri]

Hi Peter,

I remember seeing this but the criteria about working only on Mac and
Windows makes it a challenge, in my opinion.

I also need to apologize as I certainly confused the Dockerfiles between
the Maven plugin and the Docker Hub.  My prior email should have been
directed toward the Maven scenario as that is using the ADD.  Docker Hub
will just require an updating of the curl command to the .zip extension and
we should be set.  Regardless, Andy, when you make the issue for this
change feel free to create a subtask of that to update the Dockerfiles.
Looks like Peter is up to the task but I am also happy to help make the
adjustments and verify.  The first linked item you provided is the
multistage approach mentioned.  Multistage builds allow you to effectively
create throw away images only selecting specific artifacts from them to use
in a new image.

Thanks!
--aldrin

On Fri, Jun 29, 2018 at 7:11 AM Peter Wilcsinszky <
peterwilcsins...@gmail.com> wrote:

> Hi,
>
> I wrote about a different solution for which I implemented a PoC for in
>
> https://lists.apache.org/thread.html/6122674030b8f99a63d586dcdbdaf6b31841572aed63fcc9dcfb5eea@%3Cdev.nifi.apache.org%3E
> but multistage build could be a better option and I'm happy to create an
> issue and fix it for the next release.
>
> On Fri, Jun 29, 2018 at 3:42 AM Andy LoPresto 
> wrote:
>
> > Thanks Aldrin. I am not knowledgeable on Docker — do either of these
> > options help us? We could also use a RUN to curl the Zip resource and
> COPY
> > the unzipped directory?
> >
> > [1] https://github.com/moby/moby/issues/15036#issuecomment-322177465
> > [2] https://github.com/jlhawn/dockramp
> >
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Jun 28, 2018, at 6:22 PM, Aldrin Piri  wrote:
> >
> > Be mindful to also update the Dockerfile used for Docker Hub as this will
> > require some adjustments.  Unfortunately, the ADD instruction does not
> > support zip files.  This isn't a major inconvenience but will require a
> > multi-stage build to help keep our image size svelte.  I believe we
> should
> > be safe as we have been publishing both tarballs and zips for prior
> > releases, so the Dockerfile should still work in that scenario.
> >
> > On Wed, Jun 27, 2018 at 4:06 PM Andy LoPresto 
> > wrote:
> >
> > Thanks for everyone’s input. It seems to be a clear consensus to
> eliminate
> > .tar.gz and only provide .zip moving forward. I’d like to keep this
> > discussion thread going for another day or two to field any objections.
> > After that time (Friday-ish), I’ll create a Jira to do this unless things
> > change.
> >
> > I will probably keep the possibility to generate the .tar.gz through an
> > inactive profile to allow people who need that offering to use it. There
> > will be a subtask Jira to update the release guide moving forward as
> well.
> >
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Jun 26, 2018, at 7:52 PM, James Wing  wrote:
> >
> > It's a great idea, Andy, I strongly support just one format.  I think Zip
> > is a good choice.
> >
> > On Tue, Jun 26, 2018 at 11:16 AM Otto Fowler 
> > wrote:
> >
> > I end up using zip all the time.  zip +1
> >
> >
> > On June 26, 2018 at 13:30:33, Tony Kurc (tk...@apache.org) wrote:
> >
> > My preference is zip.
> >
> > On Tue, Jun 26, 2018, 9:21 AM Josh Elser  wrote:
> >
> >
> >
> > On 6/25/18 11:34 PM, Andy LoPresto wrote:
> >
> > Hi folks,
> >
> > I do not want to start a long-running argument or entrenched battle.
> > However, having just performed the RM duties for the latest release, I
> > believe I have identified a resource inefficiency in the fact that we
> > generate, upload, host, and distribute two compressed archives of the
> > binary which are functionally equivalent. For 1.7.0, both the .tar.gz
> > and .zip files are 1.2 GB (1_224_352_000 bytes for tar.gz vs.
> > 1_224_392_000 bytes for zip). The time to build and sign these is
> > substantial, but the true cost comes in uploading and hosting them.
> > While the fabled extension registry will save all of us from this
> > burden, it isn’t arriving tomorrow, and I think we could drastically
> > improve this before the next release.
> >
> > I have no personal preference between the two formats. I

Re: [DISCUSS] Tar + Gzip vs. Zip

[Aldrin Piri]

Be mindful to also update the Dockerfile used for Docker Hub as this will
require some adjustments.  Unfortunately, the ADD instruction does not
support zip files.  This isn't a major inconvenience but will require a
multi-stage build to help keep our image size svelte.  I believe we should
be safe as we have been publishing both tarballs and zips for prior
releases, so the Dockerfile should still work in that scenario.

On Wed, Jun 27, 2018 at 4:06 PM Andy LoPresto  wrote:

> Thanks for everyone’s input. It seems to be a clear consensus to eliminate
> .tar.gz and only provide .zip moving forward. I’d like to keep this
> discussion thread going for another day or two to field any objections.
> After that time (Friday-ish), I’ll create a Jira to do this unless things
> change.
>
> I will probably keep the possibility to generate the .tar.gz through an
> inactive profile to allow people who need that offering to use it. There
> will be a subtask Jira to update the release guide moving forward as well.
>
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com *
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jun 26, 2018, at 7:52 PM, James Wing  wrote:
>
> It's a great idea, Andy, I strongly support just one format.  I think Zip
> is a good choice.
>
> On Tue, Jun 26, 2018 at 11:16 AM Otto Fowler 
> wrote:
>
> I end up using zip all the time.  zip +1
>
>
> On June 26, 2018 at 13:30:33, Tony Kurc (tk...@apache.org) wrote:
>
> My preference is zip.
>
> On Tue, Jun 26, 2018, 9:21 AM Josh Elser  wrote:
>
>
>
> On 6/25/18 11:34 PM, Andy LoPresto wrote:
>
> Hi folks,
>
> I do not want to start a long-running argument or entrenched battle.
> However, having just performed the RM duties for the latest release, I
> believe I have identified a resource inefficiency in the fact that we
> generate, upload, host, and distribute two compressed archives of the
> binary which are functionally equivalent. For 1.7.0, both the .tar.gz
> and .zip files are 1.2 GB (1_224_352_000 bytes for tar.gz vs.
> 1_224_392_000 bytes for zip). The time to build and sign these is
> substantial, but the true cost comes in uploading and hosting them.
> While the fabled extension registry will save all of us from this
> burden, it isn’t arriving tomorrow, and I think we could drastically
> improve this before the next release.
>
> I have no personal preference between the two formats. In earlier days,
> there were platform inconsistencies and the tools weren’t available on
> all systems, but now they are pretty standard for all users. This [1]
>
> is
>
> an interesting article I found which had some good info on the origins,
> and here are some additional resources for anyone interested [2][3]. I
> don’t care which we pick, but I propose removing one of the options for
> the build going forward (toolkit as well).
>
> That said, if someone has a good reason that both are necessary, I
>
> would
>
> love to hear it. I didn’t find anything on the Apache Release Policy
> which stated we must offer both, but maybe I missed it. Thanks.
>
>
> I'm not aware of any ASF policy. I think it mostly stems from default
> convention you get out of the maven-assembly-plugin.
>
> [1] https://itsfoss.com/tar-vs-zip-vs-gz/
> [2] https://superuser.com/a/1257441/40003
> [3] https://superuser.com/a/173995/40003
> [4] https://www.apache.org/legal/release-policy.html#artifacts
>
>
> 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 MiNiFi 0.5.0 RC2

[Aldrin Piri]

+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/
> *
>
> 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, 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!
>

Re: Upgrading NiFi Registry

[Aldrin Piri]

I don't know that it necessarily needs to be changed but the convention we
have in other images where we make use of a wrapper init script gives a
little more flexibility for investigating/manipulating instance internals.
That convention would have made things a bit more straightforward for this
scenario.  In terms of the signals handling, I was a bit surprised they
weren't being picked up by Java but would need to investigate a bit more to
see if it was just my hastiness or if there is something else at play.

On Thu, Jun 28, 2018 at 2:33 PM Kevin Doran  wrote:

> Thanks Aldrin! That sequence makes sense to me and should result in a
> clean copy of the H2 Database. Mike, you're probably aware of this, but you
> will also want to grab the files in the HOME/flow_storage directory
> assuming those were left I nthe default settings and are not on your Docker
> volume.
>
> Aldrin, is there anything you see regarding the Registry Docker image that
> could be improved, for which we could open a JIRA? Just curious to get your
> insight while it is fresh in your mind.
>
> Thanks!
> Kevin
>
> On 6/28/18, 14:24, "Aldrin Piri"  wrote:
>
> Hi Mike,
>
> Registry's docker image is a little off from some of the other NiFi
> project
> configurations but the following approach should be fine and is fairly
> conservative in how it is carried out.
>
>1. Exec into the container - *docker exec -it name/id> /bin/bash*
>2. Inside container: stop Registry, and have your interactive
> session
>terminated as PID 1 was terminated - *./bin/nifi-registry.sh stop*
>3. On your host, copy the h2 file to your host - *docker cp
> container name/id>
> **/opt/nifi-registry/nifi-registry-0.1.0/database/nifi-registry.mv.db
>*
>4. Copy the database file in question to your volume for your new
>instance
>5. Start the new container to verify import/migration
>6. Cleanup the old container and files as appropriate
>
> 1 & 2 are questionable in terms of their necessity but with the
> potential
> for the container to get sigkilled, lend to a safer approach.  The Java
> process doesn't seem to handle the sigterm from my quick testing of
> docker
> stop.
>
> You have the ability to restart where you left off on the original
> container via *docker start ***.
>
> I did a quick run through of these steps with vanilla versions of
> 0.1.0 and
> 0.2.0 and it seemed to work as anticipated.
>
> Let us know how it goes.
>
> On Thu, Jun 28, 2018 at 1:52 PM Kevin Doran  wrote:
>
> > Oh right. My mistake. Not sure if there is a way to stop the nifi
> registry
> > process without stopping the container. Other's more knowledgeable of
> > Docker might know... In that case I'd say it's worth a shot as that
> DB file
> > should be valid so long as nothing is being written to it.
> >
> > The adoption of the git persistence provider stuff is probably still
> small
> > given how new it is, but anecdotally, I've been using it for about a
> week
> > now, syncing to a github repo as a remote, and I've not run into any
> issues
> > with it nor have I heard of anyone else having a problem with it. It
> seems
> > pretty solid to me. One of the nice things about the git option is
> that the
> > format saved to git in the snapshots is compatible with a tool like
> NiFi
> > CLI, so (while some custom scripting still required), you should be
> in a
> > pretty good position to do disaster recovery to recreate a NiFi
> Registry
> > instance with your bucket/flow/flow-snapshot data just from the
> contents of
> > your git repository should you need to for whatever reason (again,
> would
> > need to script the right NiFi CLI commands to crawl the git
> directory tree,
> > but it's pretty straightforward as it's just a matter of parsing
> json and
> > yml files). One really nice feature is that deletes (a flow or
> bucket for
> > instance) happen as a new commit so you can even recover objects
> that were
> > deleted from NiFi Registry by accident, for instance.
> >
> > If your team/users are using NiFi Registry and have feedback,
> positive or
> > otherwise, let us know as it would be great to factor that in to the
> > existing backlog for what to target in future releases.
> >
> > Best,
> > Kevin
> >
> > If your team runs into any trouble with this,

Re: Upgrading NiFi Registry

[Aldrin Piri]

Hi Mike,

Registry's docker image is a little off from some of the other NiFi project
configurations but the following approach should be fine and is fairly
conservative in how it is carried out.

   1. Exec into the container - *docker exec -it  /bin/bash*
   2. Inside container: stop Registry, and have your interactive session
   terminated as PID 1 was terminated - *./bin/nifi-registry.sh stop*
   3. On your host, copy the h2 file to your host - *docker cp 
**/opt/nifi-registry/nifi-registry-0.1.0/database/nifi-registry.mv.db
   *
   4. Copy the database file in question to your volume for your new
   instance
   5. Start the new container to verify import/migration
   6. Cleanup the old container and files as appropriate

1 & 2 are questionable in terms of their necessity but with the potential
for the container to get sigkilled, lend to a safer approach.  The Java
process doesn't seem to handle the sigterm from my quick testing of docker
stop.

You have the ability to restart where you left off on the original
container via *docker start ***.

I did a quick run through of these steps with vanilla versions of 0.1.0 and
0.2.0 and it seemed to work as anticipated.

Let us know how it goes.

On Thu, Jun 28, 2018 at 1:52 PM Kevin Doran  wrote:

> Oh right. My mistake. Not sure if there is a way to stop the nifi registry
> process without stopping the container. Other's more knowledgeable of
> Docker might know... In that case I'd say it's worth a shot as that DB file
> should be valid so long as nothing is being written to it.
>
> The adoption of the git persistence provider stuff is probably still small
> given how new it is, but anecdotally, I've been using it for about a week
> now, syncing to a github repo as a remote, and I've not run into any issues
> with it nor have I heard of anyone else having a problem with it. It seems
> pretty solid to me. One of the nice things about the git option is that the
> format saved to git in the snapshots is compatible with a tool like NiFi
> CLI, so (while some custom scripting still required), you should be in a
> pretty good position to do disaster recovery to recreate a NiFi Registry
> instance with your bucket/flow/flow-snapshot data just from the contents of
> your git repository should you need to for whatever reason (again, would
> need to script the right NiFi CLI commands to crawl the git directory tree,
> but it's pretty straightforward as it's just a matter of parsing json and
> yml files). One really nice feature is that deletes (a flow or bucket for
> instance) happen as a new commit so you can even recover objects that were
> deleted from NiFi Registry by accident, for instance.
>
> If your team/users are using NiFi Registry and have feedback, positive or
> otherwise, let us know as it would be great to factor that in to the
> existing backlog for what to target in future releases.
>
> Best,
> Kevin
>
> If your team runs into any trouble with this, do let us know as I'm not
> sure the deployment footprint
>
> On 6/28/18, 13:31, "Mike Thomsen"  wrote:
>
> Kevin,
>
> The problem with our situation is that it's all inside Docker so I
> don't
> think I can just stop the registry and proceed. That's why I was
> asking if
> it sounded feasible to just say "hands off for 5 minutes while we copy
> the
> data."
>
> Also, what is the maturity level of the GitFlow option at this point?
> That
> was particularly attractive as a storage solution because it should
> make it
> much easier to export everything from our dev team to our end users.
>
> Thanks,
>
> Mike
>
> On Thu, Jun 28, 2018 at 1:28 PM Kevin Doran  wrote:
>
> > Mike,
> >
> > I don't know the extent of H2's capabilities, but for NiFi Registry
> > changing the location of those files will require restarting the
> server to
> > pick up the new database location from nifi-registry.properties,
> correct?
> > So if I follow correctly what the objective is, my recommendation
> would be
> > the following steps:
> >
> > 1. Stop NiFi Registry
> > 2. Move/copy the H2 database files to the Docker volume location
> (should
> > be safe to do when Registry is stopped)
> > 3. Change nifi-registry.properties to point the database config
> props to
> > the new location
> > 4. Start NiFi Registry
> >
> > If the goal is actually just to copy a snapshot of the H2 database
> to the
> > docker volume and not re-point NiFi Registry, which you want to keep
> > running, I suppose you could do that. It should be fine to copy it if
> > nothing is being written, but of course no guarantees and YMMV, so
> at the
> > least I'd try to verify that it is a validate db file after copying
> it,
> > using something like [1].
> >
> > [1]
> >
> https://stackoverflow.com/questions/32727588/how-to-check-h2-database-health-and-corruption
> >
> > Hope this helps,
> > Kevin
> >
> > On 

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0

[Aldrin Piri]

Hi Jeremy,

Through the course of validation, I also saw an issue with dependencies in
support of the SiteToSite Prov Reporting Task.  This should be resolved
before release.  I would be in favor of an RC2 to remedy the hash issues as
well as incorporate a fix for the aforementioned issue, filed as MINIFI-460
[1].

[1] https://issues.apache.org/jira/browse/MINIFI-460

On Thu, Jun 28, 2018 at 9:36 AM Aldrin Piri  wrote:

> Build was okay but looks like the hashes aren't matching for the artifacts
> in the ASF repo and those in the email.
>
> On Tue, Jun 26, 2018 at 4:12 PM Jeremy Dyer  wrote:
>
>> Hello,
>>
>> I am pleased to call this vote for the source release of Apache NiFi
>> MiNiFi
>> minifi-0.5.0.
>>
>> The source zip, including signatures, digests, etc. can be found at:
>> *https://repository.apache.org/content/repositories/orgapachenifi-1129/
>> <https://repository.apache.org/content/repositories/orgapachenifi-1129/>*
>>
>> The Git tag is nifi-minifi-0.5.0-RC1
>> The Git commit ID is f5c15eb6e501bce02e90c48b506a997dbda14746
>> *
>> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=f5c15eb6e501bce02e90c48b506a997dbda14746
>> <
>> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=f5c15eb6e501bce02e90c48b506a997dbda14746
>> >*
>>
>> *
>> https://github.com/apache/nifi-minifi/commit/f5c15eb6e501bce02e90c48b506a997dbda14746
>> <
>> https://github.com/apache/nifi-minifi/commit/f5c15eb6e501bce02e90c48b506a997dbda14746
>> >*
>> Checksums of minifi-0.5.0-source-release.zip:
>> SHA1: da83318f2a606345d6b33aa4f89c9c2689dcf390
>> SHA256: 8b47d7085ed31b2c2e412375caafb80d988afeb2b0d65459b4a9eb49d05942b7
>>
>> 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 5:00PM EDT, 29 June 2018.
>>
>> 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!
>>
>

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0

[Aldrin Piri]

Build was okay but looks like the hashes aren't matching for the artifacts
in the ASF repo and those in the email.

On Tue, Jun 26, 2018 at 4:12 PM Jeremy Dyer  wrote:

> Hello,
>
> I am pleased to call this vote for the source release of Apache NiFi MiNiFi
> minifi-0.5.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> *https://repository.apache.org/content/repositories/orgapachenifi-1129/
> *
>
> The Git tag is nifi-minifi-0.5.0-RC1
> The Git commit ID is f5c15eb6e501bce02e90c48b506a997dbda14746
> *
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=f5c15eb6e501bce02e90c48b506a997dbda14746
> <
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=f5c15eb6e501bce02e90c48b506a997dbda14746
> >*
>
> *
> https://github.com/apache/nifi-minifi/commit/f5c15eb6e501bce02e90c48b506a997dbda14746
> <
> https://github.com/apache/nifi-minifi/commit/f5c15eb6e501bce02e90c48b506a997dbda14746
> >*
> Checksums of minifi-0.5.0-source-release.zip:
> SHA1: da83318f2a606345d6b33aa4f89c9c2689dcf390
> SHA256: 8b47d7085ed31b2c2e412375caafb80d988afeb2b0d65459b4a9eb49d05942b7
>
> 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 5:00PM EDT, 29 June 2018.
>
> 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!
>

Re: [EXT] RE: JIRA #NIFI-5327

[Aldrin Piri]

Hi Prashanth,

I have added you to the contributor role for the NiFi JIRA project and
assigned the issue to you.

On Wed, Jun 27, 2018 at 10:56 AM Prashanth Venkatesan <
prashanth.181...@gmail.com> wrote:

> Thanks Peter..
>
> On Wed, Jun 27, 2018 at 6:51 PM, Peter Wicks (pwicks) 
> wrote:
>
> > Prashanth,
> >
> > Woops, I had a fix for that test error months ago, but dropped it while
> > pushing a PR and never put in a ticket for it... I've submitted a PR with
> > the fix.
> >
> > https://github.com/apache/nifi/pull/2819
> >
> > --Peter
> >
> >
> https://issues.apache.org/jira/browse/NIFI-4561?focusedCommentId=16291838&;
> > page=com.atlassian.jira.plugin.system.issuetabpanels%
> > 3Acomment-tabpanel#comment-16291838
> >
> >
> >
> > -Original Message-
> > From: Prashanth Venkatesan [mailto:prashanth.181...@gmail.com]
> > Sent: Wednesday, June 27, 2018 1:19 AM
> > To: dev@nifi.apache.org
> > Subject: [EXT] RE: JIRA #NIFI-5327
> >
> > Hi Team,
> >
> >
> >
> > I create JIRA NIFI-5327  >
> > (
> > https://issues.apache.org/jira/browse/NIFI-5327) and wish to contribute
> > for it. I face couple of issues:
> >
> >- I can’t assign this issue to myself.
> >- After merging my code and when I run ` mvn -Pcontrib-check clean
> >install `  in my windows machine. I am getting the following error,
> >
> > [INFO] Running org.wali.TestMinimalLockingWriteAheadLog
> >
> > [ERROR] Tests run: 12, Failures: 0, Errors: 1, Skipped: 2, Time elapsed:
> > 24.552 s <<< FAILURE! - in org.wali.TestMinimalLockingWriteAheadLog
> >
> > [ERROR]
> > testRecoverFileThatHasTrailingNULBytesAndTruncation(org.wali.
> > TestMinimalLockingWriteAheadLog)
> > Time elapsed: 0.057 s  <<< ERROR!
> >
> > java.nio.channels.OverlappingFileLockException
> >
> > at
> > org.wali.TestMinimalLockingWriteAheadLog.testRecoverFileThatHasTrailing
> > NULBytesAndTruncation(TestMinimalLockingWriteAheadLog.java:503)
> >
> >
> >
> > Thanks & Regards,
> >
> > Prashanth
> >
>
>
>
> --
> *With regards,*
> Prashanth V
>

Re: [DISCUSS] Release Apache NiFi MiNiFi 0.5.0

[Aldrin Piri]

Yeah, I believe we are down to just two issues listed here to be reviewed:
https://issues.apache.org/jira/browse/MINIFI-459?jql=project%20%3D%20MINIFI%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%200.5.0

Otherwise, it looks like the pending items have been taken care of and we
can move forward.

Thanks for taking on the RM duties!

On Mon, Jun 25, 2018 at 10:21 PM Jeremy Dyer  wrote:

> Aldrin - Yep I'm happy to play the role of RM for this release. Now that
> NiFi 1.7.0 has been released seems like the only remaining tasks are to
> update the dependencies. Let me know if you want any help with that as well.
>
> Thanks,
> Jeremy Dyer
>
> Thanks - Jeremy Dyer
> 
> From: Kevin Doran 
> Sent: Sunday, June 24, 2018 11:04:26 PM
> To: dev@nifi.apache.org; dev@nifi.apache.org
> Subject: Re: [DISCUSS] Release Apache NiFi MiNiFi 0.5.0
>
>
>
>
>
>
>
>
> Sounds good to me. Thanks, Aldrin.
>
>
>
> Get Outlook for iOS
>
>
>
>
>
> On Sun, Jun 24, 2018 at 3:04 PM -0400, "Andy LoPresto" <
> alopresto.apa...@gmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> +1, excited to get the new stuff into MiNiFi.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jun 22, 2018, at 19:03, Aldrin Piri  wrote:
> >
> > Hello folks,
> >
> > With the NiFi vote under way, I was thinking it was an appropriate time
> to
> > start discussion around the release of 0.5.0.  There have been some
> > important fixes as well as some initial support for integration with
> > Registry.  I think we should get MiNiFi upgraded to 1.7.0 dependencies
> when
> > that release successfully completes and start the release process.
> >
> > It seems Jeremy already made a ticket to do so.  Jeremy, are you
> > volunteering to RM?  If not, I am happy to do so if no one else has any
> > interest.
> >
> > Thanks!
> > Aldrin
>
>
>
>
>
>

Re: How would we handle this?

[Aldrin Piri]

Mike,

That sounds fair and should be straightforward.  Just be sure to update the
LICENSE with the appropriate reference to the source as a derived work.

On Sat, Jun 23, 2018 at 1:46 PM Mike Thomsen  wrote:

> Aldrin,
>
> Ticket 5084 calls for a GenerateRecord processor, and this avro generator
> does a really good job of handling that. As far as I can tell, the only GPL
> issue there it uses one annotation from findbugs. I am thinking I can
> resolve this by importing the one source file we need (the Generator.java
> linked) and removing the references to the GPL'd dependency.
>
> Anyone know if that would cause us any problems? The source file in
> question says it's ASL 2.0.
>
> Thanks,
>
> Mike
>
> On Sat, Jun 23, 2018 at 1:31 PM Aldrin Piri  wrote:
>
> > Hi Mike,
> >
> > Be careful of the findbugs annotations.  While there are other projects
> > that are indeed ALv2, it appears the canonical repo has this as LGPL [2].
> > Not sure if this is needed, but could be complicating in terms of the
> > binary assemblies we would create.
> >
> > There is a cleanroom implementation [1], but not sure how this would fit
> > into the intent of what you are trying to do.
> >
> > Could you share some context of how you would be incorporating that
> source
> > and/or library?  Be sure to also consider all dependencies any target
> > library would be incorporating.
> >
> > [1] https://github.com/stephenc/findbugs-annotations
> > [2]
> >
> >
> https://github.com/findbugsproject/findbugs/tree/master/findbugs/src/java/edu/umd/cs/findbugs/annotations
> >
> > On Sat, Jun 23, 2018 at 1:12 PM Mike Thomsen 
> > wrote:
> >
> > > Disregard... There are apparently multiple projects out there that have
> > the
> > > same name and I found one that was GPL. The one this project uses
> > > **appears** to be ASL 2.0, so I think we're good.
> > >
> > > On Sat, Jun 23, 2018 at 1:04 PM Mike Thomsen 
> > > wrote:
> > >
> > > > I found that Confluent has an Avro data generator project. Their code
> > is
> > > > ASL 2.0 with the caveat that it has a GPL dependency and they
> > reference a
> > > > GPL'd class in it. Can I bring this ASL 2.0 code into our code base
> or
> > > do I
> > > > have to treat it as GPL-tainted even if I remove the references to
> the
> > > one
> > > > annotation that was from a GPL'd library?
> > > >
> > > >
> > > >
> > >
> >
> https://github.com/confluentinc/avro-random-generator/blob/master/src/main/java/io/confluent/avro/random/generator/Generator.java
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > >
> >
>

Re: How would we handle this?

[Aldrin Piri]

Hi Mike,

Be careful of the findbugs annotations.  While there are other projects
that are indeed ALv2, it appears the canonical repo has this as LGPL [2].
Not sure if this is needed, but could be complicating in terms of the
binary assemblies we would create.

There is a cleanroom implementation [1], but not sure how this would fit
into the intent of what you are trying to do.

Could you share some context of how you would be incorporating that source
and/or library?  Be sure to also consider all dependencies any target
library would be incorporating.

[1] https://github.com/stephenc/findbugs-annotations
[2]
https://github.com/findbugsproject/findbugs/tree/master/findbugs/src/java/edu/umd/cs/findbugs/annotations

On Sat, Jun 23, 2018 at 1:12 PM Mike Thomsen  wrote:

> Disregard... There are apparently multiple projects out there that have the
> same name and I found one that was GPL. The one this project uses
> **appears** to be ASL 2.0, so I think we're good.
>
> On Sat, Jun 23, 2018 at 1:04 PM Mike Thomsen 
> wrote:
>
> > I found that Confluent has an Avro data generator project. Their code is
> > ASL 2.0 with the caveat that it has a GPL dependency and they reference a
> > GPL'd class in it. Can I bring this ASL 2.0 code into our code base or
> do I
> > have to treat it as GPL-tainted even if I remove the references to the
> one
> > annotation that was from a GPL'd library?
> >
> >
> >
> https://github.com/confluentinc/avro-random-generator/blob/master/src/main/java/io/confluent/avro/random/generator/Generator.java
> >
> > Thanks,
> >
> > Mike
> >
>

[DISCUSS] Release Apache NiFi MiNiFi 0.5.0

[Aldrin Piri]

Hello folks,

With the NiFi vote under way, I was thinking it was an appropriate time to
start discussion around the release of 0.5.0.  There have been some
important fixes as well as some initial support for integration with
Registry.  I think we should get MiNiFi upgraded to 1.7.0 dependencies when
that release successfully completes and start the release process.

It seems Jeremy already made a ticket to do so.  Jeremy, are you
volunteering to RM?  If not, I am happy to do so if no one else has any
interest.

Thanks!
Aldrin

Re: [VOTE] Release Apache NiFi 1.7.0

[Aldrin Piri]

+1, binding

L&N good
hashes and signature looked good
builds passed on CentOS 7.3 and OS X
verified some simple test flows and interaction with registry

On Fri, Jun 22, 2018 at 6:02 PM Jeff  wrote:

> +1 (binding)
>
> Ran through the release helper guide,
> Built the RC1 source using Java 1.8.0_162
> Ran the resulting binary on Java 10.0.1, with some sample flows
> Looks good, thanks for the RM duties, Andy!
>
> On Fri, Jun 22, 2018 at 8:26 PM Tony Kurc  wrote:
>
> > +1
> >
> > Verified hashes and signature.
> > Notice and license look good
> > Built okay on my Ubuntu 16.04 box. Had a few problems on my windows 10
> box,
> > but believe them to be environment rather than a problem with the build
> > Ran a few test flows
> >
> >
> > On Fri, Jun 22, 2018, 3:48 PM Scott Aslan  wrote:
> >
> > > +1 binding
> > >
> > > Went through the release helper guide
> > > Tested unsecured standalone NiFi + unsecured NiFi Registry (0.2.0)
> > >
> > > Thanks for RM'ing A-Lo!
> > >
> > > On Fri, Jun 22, 2018 at 2:17 PM Andrew Lim  >
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > -Ran full clean install on OS X (10.11.6)
> > > > -Tested integration with NiFi Registry (0.2.0)
> > > > -Reviewed resolved “Core UI” component Jiras and spot checked
> inclusion
> > > in
> > > > build
> > > > -Reviewed documentation.  Found one minor issue with an image in the
> > User
> > > > Guide [1]
> > > >
> > > > Drew
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-5330
> > > >
> > > >
> > > > > On Jun 20, 2018, at 3:16 AM, Andy LoPresto 
> > > 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:
> > > >
> > >
> >
> d81e9c6eb7fc51905d6f6629b25151fc3d8af7a3cd7cbc3aa03be390c0561858d614b62d8379a90fdb736fcf5c1b4832f4e050fdcfcd786e9615a0b5cc1d563d
> > > > >
> > > > > 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

[Aldrin Piri]

+1, binding

notes:
signature and hashes look good
license and notice looked good excluding those issues already presented
verified successful integration and workflow unsecured with NiFi

On Mon, Jun 18, 2018 at 1:26 PM Scott Aslan  wrote:

> +1 binding,
>
> -ran through release helper
> -setup unsecured nifi, configured registry 0.2.0, created a bucket, placed
> PG's under version control, all looks good
>
> Thanks for RM'ing Kevin!
>
> On Mon, Jun 18, 2018 at 7:10 AM Marc  wrote:
>
> > +1 binding..
> >
> >   Stepped through helper guide for verification and validation. Looks
> > great!
> >
> > On Mon, Jun 18, 2018, 4:18 AM Pierre Villard <
> pierre.villard...@gmail.com>
> > 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 provide

Re: [VOTE] Release Apache NiFi Flow Design System 0.1.0 RC3

[Aldrin Piri]

+1, binding

comments:
* source commit looks correct
* hashes and signature looked good
* build was successful
* LICENSE and NOTICE looks good.  There was a small error referring to
Registry as being ASLv2 which should be ALv2.  A PR has been created to
correct this: https://github.com/apache/nifi-fds/pull/7
* Demo app ran successfully
* I know extremely little about npm.  Not sure if applicable but might be
helpful to list as a pre-requisite if a minimum version is needed.
Otherwise, please disregard.
* When checking out the source repository (not the voted upon distribution)
I noticed that repository is quite large at >80MB.  It seems there are two
items behind this:
  1) a nifi-registry release tag was pushed to this repo.
https://github.com/apache/nifi-fds/tree/rel/nifi-registry-0.1.0
Unfortunately, rel tags are typically protected but we should look to get
this removed from the repository with the help of INFRA (NIFI-5300),
  2) the gh-pages branch had some node modules slip in that were quite
large.  It might make sense to do a filter-branch/squash of some of these
commits as I believe this should not be an actively developed branch such
that we can bring the repo size down and remove the unnecessary binaries
(NIFI-5301)

On Tue, Jun 12, 2018 at 8:28 AM Rob Moran  wrote:

> +1
>
> * Stepped through the release guide to verify the sig, hashes, and commit
> ID
> * Checked for readme, notice, and license in source and target
> * Checked for the package version update changes
> * Ran the demo app – seems to be a slight delay initially loading up but
> all looks good
>
> Thanks for all your effort on this, Scott!
>
>
> On Tue, Jun 12, 2018 at 2:59 AM Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> > +1, binding
> >
> > Went through the release helper guide and all looks good to me AFAICT.
> > I merged the PR from Andy and set the fix version to 0.2.0.
> > (could be a good idea to ask infra for a dedicated JIRA so we don't mix
> > things regarding version numbers?)
> >
> > Congrats on this first release and thanks to everyone involved!
> >
> > Pierre
> >
> > 2018-06-12 1:02 GMT+02:00 Andy LoPresto :
> >
> > > Verified the GPG signature (SHA-512 digest, excellent) and checksums.
> > > Ran through the build and deployed, testing the demo app.
> > > Verified the LICENSE, NOTICE, and README in the source and deployable
> > > application.
> > > Checked the versioning in package.json and package-lock.json (not a
> > > JS/node expert, but I think it’s right).
> > >
> > > (One tiny typo in the README, which I fixed in a PR).
> > >
> > > +1, binding
> > >
> > > Thanks for your continued work on this release, Scott.
> > >
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > *alopresto.apa...@gmail.com *
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > On Jun 11, 2018, at 1:50 PM, Scott Aslan 
> wrote:
> > >
> > > Hello,
> > >
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > >
> > > NiFi Flow Design System 0.1.0.
> > >
> > >
> > > The source zip, including signatures, etc. can be found at:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/
> > >
> > >
> > > The Git tag is nifi-fds-0.1.0-RC3
> > >
> > > The Git commit ID is 4f62f3d4a4626f66011289c7f1346c082a932184
> > >
> > > *https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=
> > > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184
> > >  > > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184>*
> > >
> > >
> > > Checksums of nifi-fds-0.1.0-source-release.zip:
> > >
> > > SHA1:
> > >
> > > ce971d78cc0660299dcee2233bc22fa78e2940af
> > >
> > > SHA256:
> > >
> > > 7cb36f412b4147c0e071508f4f6d2ca76b2fe524382937d6552dbe7efe10a827
> > >
> > > SHA512:
> > >
> > > 11e9cf4a529862da528bd616124e57f567503c25820e4b70e72d3d53f16b
> > > fed7c0c97f05f7c390267d2163cdae2c6151dc6d9a9bdf6c11be8a6dca4409b3bd15
> > >
> > >
> > > 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
> > >
> > >
> > > 7 issues were closed/resolved for this release:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > ctId=12316020&version=12343357
> > >
> > >
> > > Release note highlights can be found here:
> > >
> > > https://cwiki.apache.org/confluence/display/NIFI/Release+
> > > Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.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.1.0
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 Do not release this package because

Re: nifi not running (installation problem) - brew

[Aldrin Piri]

Hello,

I suspect the issue is your Java version.  We are in the process of
providing support for those beyond 8.

In the interim, you can get it working via the following:

brew tap caskroom/versions
> brew update (if it doesn't do it automatically)
> brew cask install java8


I'll look to see how the formula can be adjusted until we are indeed good
for 1.8+.

--aldrin

On Thu, Jun 7, 2018 at 9:38 AM, kirilzilla  wrote:

> Hi, im writing my bachelor thesis and would like to use apache nifi.
> im using macOS 10.13.5 right now and installed nifi over brew packet
> manager
> "brew install nifi".
>
> i can't access the user interface, because nifi doesn't seem to start.
> http://localhost:8080/nifi
>
> if i run "nifi start"
> this is the output:
>
> nifi start
>
> Java home: /Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home
> NiFi home: /usr/local/Cellar/nifi/1.6.0/libexec
>
> Bootstrap Config File:
> /usr/local/Cellar/nifi/1.6.0/libexec/conf/bootstrap.conf
>
> then, when running "nifi status"
> nifi status
>
> Java home: /Library/Java/JavaVirtualMachines/jdk-10.0.1.jdk/Contents/Home
> NiFi home: /usr/local/Cellar/nifi/1.6.0/libexec
>
> Bootstrap Config File:
> /usr/local/Cellar/nifi/1.6.0/libexec/conf/bootstrap.conf
>
> *2018-06-07 15:35:08,955 INFO [main] org.apache.nifi.bootstrap.Command
> Apache NiFi is not responding to Ping requests. The process may have died
> or
> may be hung*
>
>
> my java versions:
> java --version
> java 10.0.1 2018-04-17
> Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
> Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
>
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Re: [ANNOUNCE] New NiFi PMC member Mike Thomsen

[Aldrin Piri]

Congrats and thanks for all your contributions!

On Wed, Jun 6, 2018 at 6:22 PM, Tony Kurc  wrote:

>  NiFi community,
> On behalf of the Apache NiFi PMC, I am pleased to announce that Mike
> Thomsen has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> greatly appreciate all of Mike's hard work and generous contributions to
> the project. We look forward to continued involvement in the project.
>
> Mike was announced as a committer a few months ago, and in that time I'm
> sure many have noticed Mike's increased involvement in the areas we look
> for in PMC members - building the community by helping people with issues,
> ensuring the project follows ASF best practices, participation in
> discussions, and helping others contribute (in addition to contributing his
> own code and documentation). He's been a great advocate of the project and
> of the Apache Way.
>
> Congratulations and welcome, Mike!
>
> Tony
>