Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.99.0 (RC3)

[Arpad Boda]

+1 (binding)

Built on ubuntu, verified signature and checksums. All tests passed,
started and ran a simple flow with no issues.

Nice job, team!

On Tue, May 7, 2024 at 11:35 AM Gábor Gyimesi  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> MiNiFi C++ 0.99.0.
>
> The source tarball, some binary builds, plus signatures and digests can be
> found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.99.0/
>
> The Git tag is minifi-cpp-0.99.0-RC3
> The Git commit ID is d3d205f3c8a8376bbad4c8a47758d585d57c653b
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=d3d205f3c8a8376bbad4c8a47758d585d57c653b
>
> Checksums of nifi-minifi-cpp-0.99.0-source.tar.gz:
> SHA256: c00ff309776720b295cb52ab12c1c3d11182af4f19ed0a379d58f96b16841059
> SHA512:
>
> d1eda2c19da8f0e073cf460bf889c8b4a1b893de4b245dc0147d1c79545d5298c74bedf585afd7091dc9474c923fc2a7075a81a6397bedce310e5838e3afa898
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/lordgamez.asc
>
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 121 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=12353618
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.99.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.99.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [DISCUSS] MiNiFi C++ 1.0.0-M1 release

[Arpad Boda]

+1 and thanks for RMing!

The python support in this new AI era is great!

On Thu, Apr 18, 2024 at 1:01 PM Marton Szasz  wrote:

> +1, thanks for RMing.
>
> I think we should follow the progression of the new NiFi Python API with
> the MiNiFi C++ 1.0 milestone releases, and when NiFi 2.0 is out, we
> could release MiNiFi C++ 1.0, and commit to backwards-compatibility to
> this  API.
>
> I'd exclude the C++ API, and the old MiNiFi C++-style Python and Lua
> scripting APIs out of the backwards compatibility commitment.
>
> Thanks,
> Marton
>
> On 4/16/24 6:41 PM, Pierre Villard wrote:
> > I'm a +1 with this approach. Being able to use the Python extensions in
> > MiNiFi cpp is great!
> >
> > Thanks,
> > Pierre
> >
> > Le mar. 16 avr. 2024 à 18:39, Gábor Gyimesi  a
> écrit :
> >
> >> Hi community,
> >>
> >> I'd like to initiate a discussion about the next release of MiNiFi C++.
> The
> >> last release was more than seven months ago, and there have been many
> new
> >> features, bug fixes and stability improvements committed to the
> development
> >> branch since then: 107 tickets closed, over 122 commits as of today.
> >>
> >> I would be happy to take on RM duties for this release.
> >>
> >> Notable features and improvements since the 0.15.0 release:
> >>
> >> New notable features:
> >> - Added support for using NiFi 2.0 Python processors in MiNiFi C++
> >>- This also includes several improvements to the previous MiNiFi
> style
> >> python processors, like additional property options, custom
> relationships
> >> and virtualenv support
> >> - Added new python based multiplatform bootstrap script
> >> - Added encryption support for sensitive properties in flow
> configuration
> >> - Releasing Windows installer now can be done (and will be done) under
> the
> >> Apache license
> >> - Added support for service installation on MacOS
> >> - Added C2 debug command to MiNiFi Controller
> >> - Added support for setting MiNiFi properties from command line
> >> - Added system load average field to C2 and Prometheus metrics
> >> - Added support for manually configuring RocksDB options
> >> - Added custom delimiter property for ListenTCP processor
> >> - Added bandwidth limit properties to InvokeHTTP processor
> >> - Added JSON flow configuration examples
> >>
> >> New processors:
> >> - Added PutSmb, FetchSmb and ListSmb processor for SMB networking
> protocol
> >> support
> >> - Added PushGrafanaLokiGrpc and PushGrafanaLokiREST processors for
> pushing
> >> logs to Grafana Loki
> >> - Added JoltTransform to use Jolt JSON transformations
> >> - Added SplitText processor
> >> - Added AttributeRollingWindow processor
> >>
> >> Changes and improvements:
> >> - Dropped support for disabling peer verification in InvokeHTTP
> >> - Corrupt flow files are now filtered to avoid errors in the flow
> >> - Using administrative yield duration instead of onschedule retry
> interval
> >> in scheduling adjusting to NiFi's functionality
> >> - Fixed high disk IO usage issue with MergeContent
> >> - Fixed the site-to-site transfer or large files
> >> - Fixed memory leak caused by unused loggers
> >> - Fixed yielding processors to still respect scheduling period
> >>
> >> Upgraded dependencies:
> >> - Upgraded OpenSSL to version 3.3.0
> >> - Upgraded AWS SDK to version 1.11.219 with support for new AWS regions
> >> - Upgraded libuvc to version 0.0.7
> >> - Upgraded docker base image to alpine:3.18
> >> - Upgraded Sol2 to version 3.3.0
> >>
> >> With the current maturity level of the project and with the support for
> >> NiFi 2.0 style python processors and json flow configuration, I suggest
> >> releasing it as version 1.0.0-M1 milestone release.
> >>
> >> Do you agree it is time for a new release? Do you agree with the
> suggested
> >> version? Are there any blockers that we should definitely include in
> this
> >> release?
> >>
> >> Thanks,
> >> Gabor
> >>

Re: MiNiFi C2 Module Removal

[Arpad Boda]

Thanks, David,

At the moment I don't see anyone maintaining it, so some docs should be
updated to make it clear that it's not part of the 2.0 line anymore,
otherwise I don't see any better solution.

Regards,
Arpad

On Mon, Jan 22, 2024 at 11:35 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Arpad,
>
> Thanks for the reply.
>
> I submitted a pull request [1] which deletes the modules from the main
> branch. As described in the Jira issues, the purpose is to eliminate
> maintenance of the C2 server components as they stand.
>
> [1] https://github.com/apache/nifi/pull/8291
>
> Regards,
> David Handermann
>
> On Mon, Jan 22, 2024 at 4:33 PM Arpad Boda 
> wrote:
> >
> > David,
> >
> > Thanks for bringing up this topic!
> > How do you mean removing it? Moving it into a different repo?
> >
> > Thanks,
> > Arpad
> >
> > On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
> > exceptionfact...@apache.org> wrote:
> >
> > > Team,
> > >
> > > In the process of reviewing the repository for NiFi 2.0.0 release
> > > planning, it looks the minifi-c2 bundle of modules should be
> > > considered for removal from the repository.
> > >
> > > NIFI-9428 [1] describes the general effort around MiNiFi command and
> > > control, including a task to create a C2 server reference
> > > implementation. Based on the passage of time and the lack of changes,
> > > removing the MiNiFi C2 server modules from the repository seems to be
> > > the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> > > reference implementation were to be created, it would be better to
> > > start with a clean slate, as outlined in the reference Jira issue.
> > >
> > > I have captured the proposal in NIFI-12657 [2] and I will be
> > > submitting a pull request to implement the removal.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-9428
> > > [2] https://issues.apache.org/jira/browse/NIFI-12657
> > >
>

Re: MiNiFi C2 Module Removal

[Arpad Boda]

David,

Thanks for bringing up this topic!
How do you mean removing it? Moving it into a different repo?

Thanks,
Arpad

On Mon, Jan 22, 2024 at 11:29 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> In the process of reviewing the repository for NiFi 2.0.0 release
> planning, it looks the minifi-c2 bundle of modules should be
> considered for removal from the repository.
>
> NIFI-9428 [1] describes the general effort around MiNiFi command and
> control, including a task to create a C2 server reference
> implementation. Based on the passage of time and the lack of changes,
> removing the MiNiFi C2 server modules from the repository seems to be
> the best approach as part of NiFi 2.0.0 release efforts. Even if a new
> reference implementation were to be created, it would be better to
> start with a clean slate, as outlined in the reference Jira issue.
>
> I have captured the proposal in NIFI-12657 [2] and I will be
> submitting a pull request to implement the removal.
>
> Regards,
> David Handermann
>
> [1] https://issues.apache.org/jira/browse/NIFI-9428
> [2] https://issues.apache.org/jira/browse/NIFI-12657
>

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

[Arpad Boda]

+1 (binding)

Verified signature, hashes.
Built on debian and mac.

Executed all tests successfully, verified c2 functionality, designed
multiple flows, verified those.

Thanks,
Arpad


On Wed, Aug 30, 2023 at 7:11 PM Gábor Gyimesi  wrote:

> +1 (non-binding)
>
> Went through the verification process using the helper guide.
>
> Compiled all but the JNI extension successfully on Ubuntu 22.04 with
> GCC 11, ran all unit and integration tests, did not find any issues.
>
> Compiled on Windows using MSVC and Ninja using Visual Studio 2019.
> Used the following command: win_build_vs.bat build /NINJA /P /K /S /A
> /SFTP /PDH /SPLUNK /GCP /ELASTIC /Z /PR /ENCRYPT_CONFIG /MQTT /OPC
> /PYTHON_SCRIPTING
> I had a compilation issue on Windows with the SFTP extension: linking
> SFTPLoader.cpp.obj failed with unresolved Curl symbols. Seems to be an
> issue of the static linkage of Curl, which is worth investigating, but
> I don't think it's a blocking issue. After removing SFTP from the
> compilation list the project compiled successfully.
>
> Ran two flows on both Windows (using the compiled binaries) and Linux
> (using the provided convenience binaries) successfully:
> TailFile -> LogAttribute
> GenerateFlowFile -> UpdateAttribute -> MergeContent -> CompressContent
> -> PutS3Object
>
> Note: Updated the
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139627733
> wiki page with the new OpenSSL build requirements on Windows.
>
> Thanks,
> Gábor
>
> On Tue, 29 Aug 2023 at 23:05, Marton Szasz  wrote:
> >
> > +1 (binding)
> >
> > Verified everything according to the release helper guide.
> >
> > On linux, bootstrap.sh installs all the required dependencies for
> > compiling with GCC.
> > - Ubuntu 22.04 / GCC: works fine
> > Clang required additional packages: clang libc++-dev libc++abi-dev
> > - Ubuntu 22.04 / Clang + libc++: didn't compile, but this is not a
> > showstopper IMO. We can fix it later and prepare the next release a
> > bit sooner.
> > - Ubuntu 22.04 / Clang + libstdc++: works fine
> >
> > Arch Linux / any compiler: linker issues related to curl. I wouldn't
> > tank the release for this.
> >
> > Windows steps:
> > 1. Used Visual Studio Community 2019 (VS2022 support is under review,
> > not yet included)
> > 2. Installed scoop (in powershell):> irm get.scoop.sh | iex
> > 3. Installed the latest cmake (for build), python (for scripting
> > support), sccache (for build caching, like ccache) and wixtoolset (for
> > installer generation) with scoop:> scoop install cmake python sccache
> > wixtoolset
> > 4. Source checked out at C:\a\m (to avoid long path issues)
> > 5. Built in "x64 Native Tools Command Prompt for VS2019" with the
> > following command:> win_build_vs.bat ..\bld /64 /P /K /S /A /SFTP /PDH
> > /SPLUNK /GCP /ELASTIC /Z /PR /ENCRYPT_CONFIG /MQTT /OPC
> > /PYTHON_SCRIPTING /D /NONFREEUCRT /SCCACHE
> > 6. Installed the resulting MSI, and copied cwel_config.yml from the
> > repo, but modified it to send the logs with PutTCP and PutUDP (2
> > separate tests) to a netcat listening on a linux box. It worked well,
> > the logs arrived right away on the other box. Also tried the new saved
> > log file support.
> >
> > My reaction to Ferenc's issues:
> > - I agree that we should make 64bit the default in the future.
> > - I also ran into the cpack issue in the past, but we have a note
> > about it in the README, which is good enough for now IMO.
> > - I prefer not starting the service right after installation, before I
> > even have the chance to add my flow to config.yml, but C2 users may
> > have different preferences.
> >
> > Thanks,
> > Márton
> >
> >
> >
> >
> >
> >
> > On Tue, Aug 29, 2023 at 3:20 PM Ferenc Gerlits 
> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Verified hashes and signature on the source tarball, checked git
> > > commit hash and tag.
> > > Built on Windows 10 with 64-bit VS 2019, installed the msi package and
> > > ran a simple CWEL -> LogAttribute flow.
> > >
> > > I ran into some issues during the build, but none of them are
> showstoppers:
> > >  - the release helper guide should make it clear that win_build_vs.bat
> > > defaults to 32-bit and you have to
> > >  add /64 to the command line if you want a 64-bit build (should we
> > > make 64-bit the default?);
> > >  - win_build_vs.bat fails if the build directory path contains spaces;
> > >  - the cpack command in win_build_vs.bat found chocolatey on my
> > > computer instead of CMake's cpack;
> > >  - the installer does not start the service (I don't know if it used
> > > to, but I think it should).
> > >
> > > Thank you,
> > > Ferenc
>

Re: [DISCUSS] MiNiFi C++ 0.15.0 release

[Arpad Boda]

+1

On Thu, Aug 24, 2023 at 5:22 PM Gábor Gyimesi  wrote:

> +1
>
> On Thu, 24 Aug 2023 at 17:15, David Handermann
>  wrote:
> >
> > +1
> >
> > On Thu, Aug 24, 2023 at 10:14 AM Marton Szasz  wrote:
> > >
> > > +1. I'm not aware of any blockers. Thanks for taking on RM duties.
> > >
> > > On Thu, Aug 24, 2023 at 5:04 PM Joe Witt  wrote:
> > > >
> > > > +1 a lot of nice things in there!
> > > >
> > > > On Thu, Aug 24, 2023 at 7:52 AM Martin Zink 
> wrote:
> > > >
> > > > > Hi community,
> > > > >
> > > > > I'd like to initiate a discussion about the next release of MiNiFi
> C++. The
> > > > > last release was more than four months ago, and there have been
> many new
> > > > > features, bug fixes and stability improvements committed to the
> development
> > > > > branch
> > > > > since then: 71 tickets closed, over 96 commits as of today.
> > > > >
> > > > > I would be happy to take on RM duties for this release.
> > > > >
> > > > > Notable features and improvements since the 0.14.0 release:
> > > > >
> > > > > - ConsumeWindowsEventLog can work from log files
> > > > > - ConsumeWindowsEventLog resolve Security/UserID attribute
> > > > > - TLS v1.3 support
> > > > > - PutS3Object multipart upload support
> > > > > - Use systemd service management on Linux
> > > > > - Add ProcessContext::getStateManager to Lua/Python
> > > > > - Reworked GetTCP to be more inline with ListenTCP
> > > > > - SSL support for Prometheus reporter
> > > > > - Documentation improvements
> > > > > - Multiarch docker support
> > > > > - RFC3339 parsing with expression language
> > > > > - Reworked Minifi controller
> > > > > - gcc-13 support
> > > > >
> > > > > - Fix for waking up prematurely after processor yields
> > > > > - Fix system certificate store usage in SSLContextService on Linux
> > > > > - Fix inconsistent naming in C2 machineArch
> > > > > - Fix default CA path for S3 on CentOS
> > > > > - Removed CronScheduler locale requirements
> > > > >
> > > > > We've upgraded our third party dependencies (notable mentions)
> > > > > - Replaced LibreSSL with OpenSSL 3.1.1
> > > > > - Upgraded RocksDB to v8.1.1
> > > > > - Upgraded LibCurl to v8.1.0
> > > > > - Upgraded CivetWeb to v1.16
> > > > > - Upgraded OpenCV to v4.7.0
> > > > > - Upgraded GoogleCloud SDK to v2.10.1
> > > > > - Upgraded Azure SDK to v12.7.0
> > > > >
> > > > > The core API is still not mature enough to be able to commit to
> it, so
> > > > > in line with previous discussions I suggest releasing it as 0.15.0.
> > > > >
> > > > > Do you agree it is time for a new release? Are there any blockers
> that we
> > > > > should definitely include in this release?
> > > > >
> > > > > Thanks,
> > > > > Martin
> > > > >
>

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

[Arpad Boda]

+1 (binding)

Verified signature, hashes. Built on Mac with JDK 17, created and ran a
simple flow.

On Thu, Jul 27, 2023 at 1:49 AM Joe Witt  wrote:

> +1 (binding)
>
> sigs/hashes
> Full clean build with basic flow up and running
> JDK 17
>
> On Wed, Jul 26, 2023 at 5:37 PM Emilio Setiadarma <
> emiliosetiada...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > Verified signature and SHA256/512 hashes of the release.
> > OS: MacOS Monterrey 12.6.5
> > Java version: OpenJDK version 17.0.7
> > Ran the latest build, booted up NiFi with no issues and started up a
> simple
> > NiFi flow
> >
> > Thanks David!
> >
> > On Wed, Jul 26, 2023 at 2:10 PM Matt Burgess 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Ran through release helper, verified H2 migration on Registry,
> > > ExtractRecordSchema, various other flows to ensure no regressions.
> > >
> > > Thanks for RM'ing David!
> > >
> > > On Tue, Jul 25, 2023 at 5:33 PM David Handermann
> > >  wrote:
> > > >
> > > > Team,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi
> > > > 1.23.0.
> > > >
> > > > Please review the following guide for how to verify a release
> candidate
> > > > build:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > >
> > > > The source being voted upon and the convenience binaries are
> available
> > on
> > > > the Apache Distribution Repository:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.0/
> > > >
> > > > The build artifacts are available on the Apache Nexus Repository:
> > > >
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1233
> > > >
> > > > Git Tag: nifi-1.23.0-RC3
> > > > Git Commit ID: 27a690a30a6ae77c217a47ac0601e85970777ca2
> > > > GitHub Commit Link:
> > > >
> > >
> >
> https://github.com/apache/nifi/commit/27a690a30a6ae77c217a47ac0601e85970777ca2
> > > >
> > > > Checksums of nifi-1.23.0-source-release.zip:
> > > >
> > > > SHA256:
> > 39c97d89804b005cc995c56a87a3df6f68c44ee42114dffe756bbac90a3593cf
> > > > SHA512:
> > > >
> > >
> >
> f256ca731a67435e9883626931abc58f28cda9deb6a7d0a84ed97b78104e43b3b638ee2297d79f92bf5a1e19f62cc78e0a886fa0094593ab34b21d658c59eadd
> > > >
> > > > Release artifacts are signed with the following key:
> > > >
> > > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > > >
> > > > KEYS file available here:
> > > >
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 132 issues were closed/resolved for this release:
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353320
> > > >
> > > > Release note highlights can be found here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.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.23.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > >
> >
>

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

[Arpad Boda]

+1 binding

Verified hashes, built on ubuntu, executed tests and created a simple flow.
All works as expected.

On Fri, Apr 14, 2023 at 7:57 PM Adam Debreceni 
wrote:

> +1 (non-binding)
>
> Verified signatures, hashes, commit. Built on ubuntu 22.04, ran tests,
> tested simple flow.
>
> Thanks!
>
> On Fri, Apr 14, 2023 at 7:12 PM Joe Witt  wrote:
>
> > +1 binding.  Was able to do full build on a linux system.  Hashes/sigs
> > check out.
> >
> > The L look good with basic spot check.  The Notice needs to be updated
> to
> > reflect the 2023 copyright year.
> >
> > Thanks!
> >
> > On Fri, Apr 14, 2023 at 9:59 AM Marton Szasz  wrote:
> >
> > > +1 (binding)
> > > The package, hashes, signatures, etc were all good. Release helper
> > > guide for future reference:
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303
> > >
> > > Tested compilation on Ubuntu 22.04 with both GCC and Clang. Tested
> > > both the self-built and the convenience binaries in a log collection
> > > use case, forwarding messages via HTTP to NiFi.
> > > Tested compilation on Windows x64, and a security event log collection
> > > use case using ConsumeWindowsEventLog, and forwarding via
> > > PutUDP/ListenUDP to NiFi.
> > >
> > > Thank you for preparing the RC!
> > >
> > > Marton
> > >
> > > On Fri, 14 Apr 2023 at 18:55, Ferenc Gerlits 
> > wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > Verified signatures and hashes, compared the source to the git tag.
> > > > Built from source on Ubuntu Linux 22.04 and Windows.
> > > > Ran the convenience binary on Ubuntu Linux 22.04 with a simple
> > > > ConsumeJournald -> PublishKafka flow.
> > > > Installed and ran the binary built from the source on Windows with a
> > > > simple ConsumeWindowsEventLog -> PublishKafka flow.
> > > > Everything worked fine.
> > > >
> > > > Thanks,
> > > > Ferenc
> > >
> >
>

Re: [DISCUSS] MiNiFi C++ 0.14.0 release

[Arpad Boda]

+1

On Mon, Apr 3, 2023 at 4:11 PM Martin Zink  wrote:

> +1, seems like a good time for a new release, thanks for RM-ing
>
> On Mon, Apr 3, 2023 at 4:07 PM Kevin Doran  wrote:
>
> >  +1 from me, it seems like a good time for the next release of MiNiFi C++
> >
> > On Apr 3, 2023 at 07:34:44, Gábor Gyimesi  wrote:
> >
> > > Hi community,
> > >
> > > I'd like to initiate a discussion about the next release of MiNiFi C++.
> > The
> > > last release was almost four months ago, and there have been many new
> > > features,
> > > bug fixes and stability improvements committed to the development
> branch
> > > since then: 74 tickets closed, over 80 commits as of today.
> > >
> > > I would be happy to take on RM duties for this release.
> > >
> > > Notable features and improvements since the 0.14.0 release:
> > >
> > > - Several improvements on repository resource handling
> > >  * Periodically run RocksDB repository compaction+1
> > >  * Add compression options for RocksDB repositories
> > >  * Add synchronous flow file reloading
> > >  * Retry failed removals of unused resources
> > > - Use Python stable ABI to support all libraries above Python 3.2+ for
> > > Python processors
> > > - Add ProcessSession::remove to Python and Lua API
> > > - Add support for JSON flow configuration format with option to
> generate
> > > JSON schema locally
> > > - Add support for reverseDnsLookup in expression language
> > > - Fix most issues for ARM64 support
> > > - Improve performance of ListFile processor
> > > - Add cache SID lookups in ConsumeWindowsEventLog processor
> > > - Add default connection size limits of 2000 queue size and 100MB of
> > queue
> > > data size
> > > - Add support for MQTT 5 (mistakenly advertised for 0.13.0 release)
> > > - Add failure relationship to SQL processors
> > > - Add support for new AWS regions
> > > - Add option to select processor metrics with regular expressions
> > > - Add the UUID to the end of Processor and Controller Service log lines
> > > - Make GetFile path attributes consistent with other processors
> > > - Fix leaks and file lock issues on Windows
> > > - Fix crashing in python processors
> > >
> > > The core API is still not mature enough to be able to commit to it, so
> > > in line with previous discussions I suggest releasing it as 0.14.0.
> > >
> > > Do you agree it is time for a new release? Are there any blockers that
> we
> > > should definitely include in this release?
> > >
> > > Thanks,
> > > Gabor
> > >
> >
>

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

[Arpad Boda]

+1 (bindig)

Built and started with a simple flow on m1 mac, verified sigs and hashes.

Thanks,
Arpad

On Thu, Dec 8, 2022 at 12:38 PM Marc Parisi  wrote:

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

Re: [DISCUSS] MiNiFi C++ 0.13.0 release

[Arpad Boda]

Ship it!

 /|~~~
   ///|
 /|
   ///|
 /|
   \==|===/
~


On Mon, Nov 28, 2022 at 5:48 PM Joe Witt  wrote:

> That is a pretty loaded set of changes.  Lets do it.
>
> Thanks
>
> On Mon, Nov 28, 2022 at 9:46 AM Kevin Doran  wrote:
> >
> >  +1, seems like a great time for a new release
> >
> > On Nov 28, 2022 at 05:14:59, Ferenc Gerlits  wrote:
> >
> > > Hi community,
> > >
> > > I'd like to initiate a discussion about the next release of MiNiFi
> C++. The
> > > last release was almost six months ago, and there have been many new
> > > features,
> > > bug fixes and stability improvements committed to the development
> branch
> > > since then: 80 tickets closed, over 100 commits.
> > >
> > > I would be happy to take on RM duties for this release.
> > >
> > > New features since the 0.12.0 release:
> > >
> > > - New processors:
> > >  * ListenTCP
> > >  * PutTCP
> > >  * PostElasticSearch
> > >  * CollectKubernetesPodMetrics
> > > - Warn on SSL certificates about to expire
> > > - Fix cron-based scheduling
> > > - Improve metrics reporting and add support for Prometheus
> > > - Improve the performance of several processors (ListenHTTP, AWS,
> Azure,
> > > GCS)
> > > - Support swapping out flow files from memory to disk
> > > - Support low-memory use cases with FileSystemRepository
> > > - Improve the MQTT processors and add support for MQTT v5.0
> > > - Improve communication with C2, eg. add alert capability
> > > - Fix support of native packages in Python scripting
> > > - Fix Python scripting on Windows
> > > - Add SSL support to the ListenSyslog and ListenTCP processors
> > > - Fix the 32-bit build on Windows
> > > - Support POST/PUT of large files in InvokeHTTP
> > > - Plus upgrade libraries, fix issues reported by clang-tidy, fix memory
> > > leaks etc
> > >
> > > The core API is still not mature enough to be able to commit to it, so
> > > in line with previous discussions I suggest releasing it as 0.13.0.
> > >
> > > Do you agree it is time for a new release? Are there any blockers that
> we
> > > should definitely include in this release?
> > >
> > > Thanks,
> > > Ferenc
> > >
>

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

[Arpad Boda]

+1 binding

Verified checksums, build, signature, started NiFi, designed a simple flow.

Thanks,
Arpad

On Sat, Nov 26, 2022 at 6:41 PM Marton Szasz  wrote:

> +1 (binding)
>
> Followed the usual steps and tested a use case of collecting system
> logs with minifi c++ and collecting them in nifi using ListenUDP.
>
> Thanks,
> Marton
>
> On Sat, 26 Nov 2022 at 06:25, David Handermann
>  wrote:
> >
> > +1 (binding)
> >
> > - Verified signatures and hashes
> > - Ran build using Maven 3.8.6
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 AMD64
> > - Ran build on macOS 13.0 with Azul Zulu JDK 17.0.4 AArch64
> > - Ran stateless and system tests on macOS 13.0 with Azul Zulu JDK 17.0.4
> > AArch64
> >
> > - Ran NiFi on macOS 13.0 with Azul Zulu JDK 17.0.4 AArch64
> > - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 AMD64
> > - Configured SAML 2 authentication and reverse proxy access
> >
> > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-345 AMD64
> > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.4 AMD64
> > - Created Buckets
> > - Verified Flow Version Control
> >
> > - NIFI-7392 Verified ValidateJson Processor with each relationship
> > - NIFI-10577 Verified visibility of sensitive checkbox on Firefox in
> Fetch
> > Parameters dialog
> > - NIFI-10506 Verified relocation of Repository Encryption to
> > Administrator's Guide
> > - NIFI-10569 Verified Maximum Threads property on HandleHttpRequest
> > - NIFI-10594 Verified visibility of multiple blank lines in Labels
> > - NIFI-10604 Verified Idle Timeout property handling in ListenTCP
> > - NIFI-10614 Verified Bouncy Castle 1.71 and jdk18on libraries across
> > modules
> > - NIFI-10624 Verified removal of sensitive properties key warning from
> > component documentation
> > - NIFI-10625 Verified HTTP/2 support in NiFi Registry
> > - NIFI-10628 Verified default Run Schedule on multiple Processors
> > - NIFI-10647 Verified updated URL in bundled README instructions
> > - NIFI-10648 Verified Apache Commons Text 1.10.0 upgraded across bundled
> > modules
> > - NIFI-10667 Verified Standard Private Key Service with valid and invalid
> > PKCS8 keys
> > - NIFI-10709 Verified presence of log in link on logout success
> > - NIFI-10713 Verified deprecation warning logged for PGP in
> EncryptContent
> > Processor
> > - NIFI-10798 Verified deprecation warning logged when running on Java 8
> > - NIFI-10819 Verified sasl.jaas.config with JndiLoginModule is invalid
> for
> > Kafka 2.6 Processors
> > - NIFI-10842 Verified optional HTTP Protocols property in OAuth2 Token
> > Provider
> > - NIFI-10861 Verified deprecation warning logged for legacy Azure Blob
> > Storage Processors
> >
> > Thanks Joe!
> >
> > Regards,
> > David Handermann
> >
> > On Wed, Nov 23, 2022 at 9:58 AM Joe Witt  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > > 1.19.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1216
> > >
> > > The source being voted upon and the convenience binaries can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.19.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.19.0-RC1
> > > The Git commit ID is ec87bf93add2f645d2ea426002e0c24db54614ff
> > >
> > >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=ec87bf93add2f645d2ea426002e0c24db54614ff
> > >
> > > Checksums of nifi-1.19.0-source-release.zip:
> > > SHA256:
> 909c4fce81b305af955540f83115474d139c132e886847df7b76e94efd3d4641
> > > SHA512:
> > >
> > >
> b3ba95984841140aa2a9a2ea471dd446d6fbd71dba320f723839e0938a7873f847e415a88b7c38e59907ad051c896949f0c7093c6d5e6b5db549de929ec32c6e
> > >
> > > 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
> > >
> > > 221 issues were closed/resolved for this release:
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12352150
> > >
> > > Release note highlights can be found here:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.19.0
> > >
> > > The vote will be open for at least 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.19.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
>

Re: Grammar error in error message

[Arpad Boda]

At your service:

https://github.com/apache/nifi/pull/6669

On Wed, Nov 16, 2022 at 6:49 PM Russell Bateman 
wrote:

> Yes it should be the infinitive */receive/* instead of the past
> participle /received/.
>
> On 11/16/22 08:18, Paul Schou wrote:
> > This error message does not look like it is grammatically correct:
> >
> >
> https://github.com/gkatta4113/nifi/blob/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/ListenHTTP.java#L332
> >
> > getLogger().warn("failed to received acknowledgment for HOLD with ID {}
> > sent by {}; rolling back session", new Object[] {id,
> > wrapper.getClientIP()});
> >
> > - Paul Schou
> >
>

Re: request for Jira contributor access

[Arpad Boda]

Hi He,

Added you to the contributor list, looking forward to your contribution!

Cheers,
Arpad

On Sat, Sep 24, 2022 at 4:02 PM heji...@tju.edu.cn 
wrote:

> Hi,
>
> My jira name is hejiang and I would like to request for Jira contributor
> access and hope to do some contribution later.
>
> Best regards,
> He Jiang

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

[Arpad Boda]

+1 (binding)

Ran through the helper guide, verified signature, checksums, commit id and
the expected behavior (both api implementations provided by cache clients).

Thanks for RM'ing Bryan and thanks Kevin for making this verification
possible on arm64!

On Wed, Jul 20, 2022 at 11:00 PM Kevin Doran  wrote:

>  +1 (binding)
>
> Ran through the steps in the Release Helper Guide; everything checked out.
>
> Thanks for the bugfix and RM'ing Bryan!
> Kevin
>
> On Jul 20, 2022 at 16:37:16, Bryan Bende  wrote:
>
> > Hello Apache NiFi Community,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi NAR Maven Plugin 1.3.5.
> >
> > The source being voted upon, including signatures, digests, etc. can
> > be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.3.5/
> >
> > The Git tag is nifi-nar-maven-plugin-1.3.5-RC1
> > The Git commit ID is 77f516a65d796b715278bedd06407d4a8f98f771
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=77f516a65d796b715278bedd06407d4a8f98f771
> >
> > Checksums of nifi-nar-maven-plugin-1.3.5-source-release.zip:
> > SHA256: 073271bbd28b3d0b9b74c42ab889b4e7301e52b9a0579a3484e7ad0b7f8d3532
> > SHA512:
> >
> 9fcc487a197a8d3c5cd297696eb303015c9cde32f89541682dfac921e862c1f1ee8ba5e41573eeb7a5b5190b95c3b49443fca9ed5d5a3f7768a4ea1b031829af
> >
> > 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
> >
> > 2 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12351862
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.5
> >
> > The vote will be open for 24 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.5
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
>

Re: [DISCUSS] MiNiFi C++ 0.12.0 release

[Arpad Boda]

+1

On Mon, May 16, 2022 at 4:12 PM Joe Witt  wrote:

> Certainly more than enough there!  Thanks Martin
>
> On Mon, May 16, 2022 at 7:06 AM Martin Zink  wrote:
>
> > Hi community,
> >
> > I'd like to initiate a discussion about the next release of MiNiFi C++.
> The
> > last release was five months ago, and there have been many new features,
> > bug fixes and stability improvements committed to the development branch
> > since. (~110 commits)
> > I would be happy to take on RM duties for this release.
> >
> > New features since the 0.11.0 release:
> > - new processors:
> >* DeleteAzureBlobStorage
> >* FetchAzureBlobStorage
> >* FetchAzureDataLakeStorage
> >* ListAzureBlobStorage
> >* ListAzureDataLakeStorage
> >* PutGCSObject
> >* ProcFsMonitor
> >* PutUDP
> >* FetchFile
> >* ListFile
> >* PutSplunkHTTP
> >* QuerySplunkIndexingStatus
> >
> > - Log collection from Kubernetes
> > - improved support for Lua processors
> > - platform independent ListenSyslog
> > - property update over C2 protocol
> >
> > The core API is still not mature enough to be able to commit to it, so
> > in line with previous discussions I suggest releasing it as 0.12.0.
> >
> > Do you agree it is time for a new release? Are there any blockers that we
> > should definitely include in this release?
> >
> > Thanks,
> > Martin
> >
>

Re: Jira contributor access

[Arpad Boda]

Hi Krisztina,

Granted, looking forward to your contributions!

Cheers,
Arpad

On Fri, May 6, 2022 at 10:56 AM Krisztina Zsihovszki 
wrote:

> Hello,
>
> I would like the JIRA access to NiFi issues. My username is *kzsihovszki*.
>
> Thank you and regards,
>
> Krisztina
>

Re: Minifi confluence write access

[Arpad Boda]

Hi Martin,

Granted, waiting for the update docs. :)

On Wed, May 4, 2022 at 3:10 PM Martin Zink  wrote:

> Hi,
>
> I would like to ask for write access to the MiNiFi space on Confluence to
> update the outdated/missing documentation on the C2 protocol.
>
> Thanks,
> Martin
> martinz...@apache.org
>

Re: Jira Contributor Access

[Arpad Boda]

Hey Pat,

Granted, looking forward to your PRs!

Cheers,
Arpad

On Wed, Mar 16, 2022 at 2:35 AM Patrick Alwell, Jr. 
wrote:

> Hey Guys,
>
> Requesting  Jira Access for contributing to NiFi.
>
> Username = pat_alwell
>
> Found a few small bugs and created patches, so will open tickets and get a
> few PRs over to ya!
>
> -Pat

Re: Contributor Access

[Arpad Boda]

Hi Steven,

Granted, looking forward to your contribution.

BR,
Arpad

On Fri, Mar 11, 2022 at 2:14 PM Steven Matison 
wrote:

> Hi just requesting access
>
> username stevenmatison
>
> Thanks,
>
> Steven
>

Re: Contributor access

[Arpad Boda]

Tamas,

Granted, looking forward to your contribution!

BR,
Arpad

On Fri, Mar 11, 2022 at 12:19 PM Horváth Tamás  wrote:

> Dear Developers,
> May I ask you to grant me contributor access to the NIFI project?
> I will make my first upstream contribution to NIFI-9786.
> My apache Jira username is thorvath
>
> Regards,
> Tamas Horvath
> Cloudera
>

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

[Arpad Boda]

+1 (binding)
Verified sigs, hashes, built on Deb 11, tested with simple flow, LGTM!

On Fri, Dec 10, 2021 at 5:03 AM Kevin Doran  wrote:

> +1 (binding)
>
> Checked sigs and hashes and did my usual docker-based build and test.
> Looks good, nice work everyone!
>
> Kevin
>
> > On Dec 8, 2021, at 11:48, Marton Szasz  wrote:
> >
> > +1 (binding)
> > Went through the usual checks, built, ran tests and packaged on gentoo
> > with gcc 11.2.1 and clang 13.0.0, then tested the convenience binary
> > on ubuntu 16.04 collecting logs with ConsumeJournald -> InvokeHTTP
> > sending it to the gentoo clang version ListenHTTP -> LogAttribute.
> >
> > Thanks,
> > Marton
> >
> > On Wed, 8 Dec 2021 at 12:17, Martin Zink  wrote:
> >>
> >> +1 (non binding)
> >> Verified the hashes and built on Manjaro and win10
> >> Tested a couple example flows (\examples\pdh_config.yml,
> >> \examples\tailfile_config.yml)
> >> Everything works as expected
> >>
> >> Thanks,
> >> Martin
> >>
> >> On Wed, Dec 8, 2021 at 1:03 PM Marc Parisi  wrote:
> >>
> >>> +1 verified sigs and hashes and ran some test flows from a local
> cluster
> >>> gathering log data sending to nifi via site to site.
> >>>
> >>> Works great!
> >>>
> >>> On Wed, Dec 8, 2021 at 6:51 AM Ádám Markovics 
> >>> wrote:
> >>>
>  +1 (non-binding)
>  Verified and built on Ubuntu 20.04. Ran tests and also ran a simple
>  (GetFile-PutFile) flow.
>  Regards,
> 
>  Ádám
> 
>  On Mon, Dec 6, 2021 at 12:06 PM Adam Debreceni  >
>  wrote:
> 
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
>  NiFi
> > MiNiFi C++ 0.11.0.
> >
> > The source tarball, the binary build, plus signatures and digests can
> >>> be
> > found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.11.0/
> >
> > The Git tag is minifi-cpp-0.11.0-RC2
> > The Git commit ID is 0553df446aefb395b34c1e4e2b5ced31f07a4e04
> >
> >
> 
> >>>
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=0553df446aefb395b34c1e4e2b5ced31f07a4e04
> >
> > Checksums of nifi-minifi-cpp-0.11.0-source.tar.gz:
> > SHA256:
> >>> 98e161436f2ae1b9eacf27493fe3420891aa5e4e70c20216ec186c5e23c2c11d
> > SHA512:
> >
> >
> 
> >>>
> 8e968d9d58ea793d1f6f064374c07ac0ef296c2fd895941ea74c879e06fc95c48100fd9c2d28bc2bc5c523c8ad229a77a5626f8311c038aeb87d8fd4324dfe0e
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/adebreceni.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 86 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/projects/MINIFICPP/versions/12350247
> >
> > Release note highlights can be found here:
> >
> >
> 
> >>>
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.11.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary
> items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-minifi-cpp-0.11.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> 
> >>>
>
>

Re: [DISCUSS] MiNiFi C++ 0.11.0 release

[Arpad Boda]

+1

On Thu, Nov 18, 2021 at 5:23 PM Ádám Markovics  wrote:

> I also agree on releasing. Let's do it!
>
> Ádám
>
> On Thu, Nov 18, 2021 at 4:05 PM Joe Witt  wrote:
>
> > Sounds like a great time to cut a new release.
> >
> > On Thu, Nov 18, 2021 at 7:32 AM Gábor Gyimesi 
> wrote:
> > >
> > > Sounds good to me as well!
> > >
> > > Thanks,
> > > Gabor
> > >
> > > On Thu, 18 Nov 2021 at 15:27, Ferenc Gerlits 
> > wrote:
> > >
> > > > Yes, it's definitely time for a new release, and 0.11.0 sounds good.
> > > > Thanks for RMing!
> > > >
> > > > Ferenc
> > > >
> > > >
> > > > On Wed, Nov 17, 2021 at 12:09 PM Marton Szasz 
> > wrote:
> > > >
> > > > > I agree that it's time for a new release, thank you for taking the
> RM
> > > > > duties. I'm not aware of any blockers at the moment.
> > > > >
> > > > > Thanks,
> > > > > Marton
> > > > >
> > > > > On Wed, 17 Nov 2021 at 10:28, Adam Debreceni <
> adebrec...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > Hi community,
> > > > > >
> > > > > > I'd like to initiate a discussion about the next release of
> MiNiFi
> > C++.
> > > > > The
> > > > > > last release was five months ago, and there have been many new
> > > > features,
> > > > > > bug fixes and stability improvements committed to the development
> > > > branch
> > > > > > since.
> > > > > > I would be happy to take on RM duties for this release.
> > > > > >
> > > > > > New features since the 0.10.0 release:
> > > > > > - new processors:
> > > > > >* AttributesToJson
> > > > > >* DefragmentText
> > > > > >* PutAzureDataLakeStorage
> > > > > >* ReplaceText
> > > > > >* RouteText
> > > > > > - support for funnels
> > > > > > - shared rocksdb repository
> > > > > > - repository encryption (flow-file, content)
> > > > > > - support for Azure managed identity
> > > > > > - modularization of extensions
> > > > > > - ConsumeKafka security protocol
> > > > > > - platform independent AppendHostInfo
> > > > > > - agent configuration checksum in the c2 heartbeat
> > > > > >
> > > > > > We now use C++17 throughout the codebase and C++20 wherever
> > possible.
> > > > > >
> > > > > > The core API is still not mature enough to be able to commit to
> > it, so
> > > > > > in line with previous discussions I suggest releasing it as
> 0.11.0.
> > > > > >
> > > > > > Do you agree it is time for a new release?  Are there any
> blockers
> > that
> > > > > we
> > > > > > should definitely include in this release?
> > > > > >
> > > > > > Thanks,
> > > > > > Adam
> > > > >
> > > >
> >
>

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

[Arpad Boda]

+1 (binding)

Built on Debian 10 using Java 11, started, designed a simple flow.
Verified hashes, signatures.

Ps.: some tests failed, so only built without them.

On Mon, Jul 12, 2021 at 12:38 PM Joe Gresock  wrote:

> +1 (non-binding)
>
> Verified signature and hashes
> Full build with contrib check with OpenJDK Runtime Environment (Zulu
> 8.54.0.21-CA-macosx) (build 1.8.0_292-b10)
> Upgraded a single secure nifi 1.13.2 cluster with an existing flow, which
> started successfully.
> Verified TLS 1.3 works using an existing flow with
> HandleHttpRequest/Response and InvokeHttp
> Restarted with nifi.security.autoreload.enabled=true and verified that I
> was able to replace a keystore and truststore while NiFi was running
> Upgraded a 3-node secure nifi 1.13.2 cluster with an existing flow, which
> started successfully.
> Verified that load balanced connections work as expected, before and after
> offloading a node.
> Used the encrypt-config.sh tool from Toolkit to encrypt nifi.properties and
> nifi-registry.properties using AES/GCM, verified both apps started
> successfully.
> Used encrypt-config.sh to migrate the encryption to the
> HASHICORP_VAULT_TRANSIT protection scheme, verified both apps started
> successfully.
> Built a DataFlow and saved to file, then ran it via Stateless NiFi, using a
> custom ParamaterProvider, verified that parameters were correctly provided.
>
> On Sun, Jul 11, 2021 at 1:33 PM Robert Fellows 
> wrote:
>
> > +1 (non-binding)
> >
> > Verified signature and hashes
> > Full build with contrib check with OpenJDK Runtime Environment
> AdoptOpenJDK
> > (build 11.0.8+10)
> > Started new instance, verified it was secured by default.
> > Changed the username and password using bin/nifi.sh
> > set-single-user-credentials
> > Logged in with the new user/password i created
> > Fired up registry, created a bucket
> > Connected nifi to registry, versioned a flow. Imported a flow into
> another
> > process group.
> > General App usage (Firefox 89.0.2)
> >
> > Thanks for RM'ing this Joe!
> >
> > -- Rob Fellows
> >
> > On Sat, Jul 10, 2021 at 9:31 PM Mark Payne  wrote:
> >
> > > +1 (binding)
> > >
> > > Verified the hashes.
> > > Performed full build with contrib-check profile
> > > Ran all system tests
> > > Started the newly created instance, verified that it was secure by
> > default.
> > > Changed username & password and verified the behavior.
> > > Created a 2-node cluster, secured by mutual TLS and verified behavior.
> > >
> > > Started nifi registry. Created a bucket.
> > > Pushed to the bucket from standalone instance. Then added a second
> > version
> > > of flow.
> > > Downloaded flow onto cluster and switched between versioned a few
> times.
> > >
> > > Verified behavior of new default backpressure thresholds.
> > > Built a DataFlow and saved to file, then ran it via Stateless NiFi
> using
> > > command-line parameter overrides.
> > > Started DataFlow using Stateless nifi and the kafka connector. Verified
> > > this behavior.
> > >
> > > Encountered no issues this time.
> > >
> > > Thanks for putting the RC together, Joe!
> > >
> > > > On Jul 10, 2021, at 6:40 PM, Joe Witt  wrote:
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > > NiFi 1.14.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1183
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/1.14.0/
> > > >
> > > > Please note that this release now includes the convenience binaries
> for
> > > > Apache NiFi, NiFi toolkit, MiNiFi, MiNiFi Toolkit, Registry, Registry
> > > Toolkit,
> > > > and Stateless NiFi.
> > > >
> > > > 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.14.0-RC2
> > > > The Git commit ID is fcbf1d5f975dd984e34f3a543b9480c779b0dc2f
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=fcbf1d5f975dd984e34f3a543b9480c779b0dc2f
> > > >
> > > > Checksums of nifi-1.14.0-source-release.zip:
> > > > SHA256:
> > a96cf75c4f82d01e1c8e0b678d5ff23dec8c26824611c8d37f2ec245e9932b1c
> > > > SHA512:
> > >
> >
> 2d23b1a2fae9f545f665c4ee5d9723cdf9c68a62a26d80287b96a55773594e1e80f689ec0f00ba74af92df164c6f4df73ac9b91db7678aaefd69ee8f1eed3f42
> > > >
> > > > 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
> > > >
> > > > 330+ issues were closed/resolved for this release:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12349644
> > > >
> > > > 

[ANNOUNCE] New NiFi PMC Member Marton Szasz

[Arpad Boda]

On behalf of the Apache NiFI PMC, I am very pleased to announce that Marton
has accepted the PMC's invitation to join the Apache NiFi PMC. We greatly
appreciate the PR reviews and code contributions of Marton.

Please join us in congratulating and welcoming Marton to the Apache NiFi
PMC.

Congratulations Marton!

[ANNOUNCE] New Apache NiFi Committer Denes Arvay

[Arpad Boda]

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

Welcome and congratulations!

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

[Arpad Boda]

+1 (binding)

Verified build and signatures on Debian 10 and Windows 10.
Executed tests, designed a simple flow and started the agent.

On Wed, Jun 9, 2021 at 1:20 PM Marton Szasz  wrote:

> +1 (non-binding)
>
> Followed the release helper guide on linux amd64. Verified the build
> and the resulting binaries with both GCC 11 and Clang 12. The flow was
> testing the new ConsumeJournald.
>
> Thanks
>
> On Wed, 9 Jun 2021 at 11:12, Martin Zink
>  wrote:
> >
> > +1 (non-binding)
> >
> > Built on windows 10 with MSVC 19.28.29337 and tested the new
> PerformanceDataMonitor processor with a simple flow
> > Also built on linux and tested the new ConsumeJournald processor with a
> simple flow
> >
> > Works as expected, great job!
> >
> > Thank you,
> > Martin
> >
> > ‐‐‐ Original Message ‐‐‐
> >
> > On Wednesday, June 9th, 2021 at 12:41, Adam Debreceni <
> adebrec...@apache.org> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Verified hashes, signature, commit. Built on macOS with everything
> enabled
> > >
> > > (bootstrap.h -e) ran all tests.
> > >
> > > Built on Windows (/K /PDH /A /64 /2019) ran all tests, deployed
> > >
> > > CWEL->LogAttribute flow through c2 protocol.
> > >
> > > Thank you,
> > >
> > > Adam
> > >
> > > On Mon, Jun 7, 2021 at 9:50 PM Ferenc Gerlits fgerl...@apache.org
> wrote:
> > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of
> Apache NiFi
> > > >
> > > > MiNiFi C++ 0.10.0.
> > > >
> > > > The source tarball, some binary builds, plus signatures and digests
> can be
> > > >
> > > > found at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.10.0/
> > > >
> > > > The Git tag is minifi-cpp-0.10.0-RC2
> > > >
> > > > The Git commit ID is 60d5bc70b567fa7c6689f313a75be17fe7c94080
> > > >
> > > >
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=60d5bc70b567fa7c6689f313a75be17fe7c94080
> > > >
> > > > Checksums of nifi-minifi-cpp-0.10.0-source.tar.gz:
> > > >
> > > > SHA256:
> f7dc86ef6e35ea0d9c9c39891ea281a9851b1e6fc382b16d3a5931814f5ebc22
> > > >
> > > > SHA512:
> > > >
> > > >
> 484d3196d087e7c1acb5d703b827929edf0d8dae295878e1f79232ab8de4fd358f12fa223201c92e0cd9e0c59f2314da9001ac12eb91eabeda751e5d46c4f6b7
> > > >
> > > > Release artifacts are signed with the following key:
> > > >
> > > > https://people.apache.org/keys/committer/fgerlits.asc
> > > >
> > > > KEYS file available here:
> > > >
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 67 issues were closed/resolved for this release:
> > > >
> > > > https://issues.apache.org/jira/projects/MINIFICPP/versions/12349956
> > > >
> > > > Release note highlights can be found here:
> > > >
> > > >
> https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-Versioncpp-0.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-minifi-cpp-0.10.0
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 Do not release this package because...
>

Re: Contributor access to Jira

[Arpad Boda]

Hi Dominik,

Added you, looking forward to your contributions!

On Mon, Jun 7, 2021 at 8:26 AM Dominik Przybysz 
wrote:

> Hi,
> can I receive contributor access to Jira project NIFI in order to assign
> https://issues.apache.org/jira/browse/NIFI-8610 to me and be able to merge
> my MR to NIFI?
> My apache id is alien11689
>
> --
> Pozdrawiam / Regards,
> Dominik Przybysz
>

Re: [DISCUSS] MiNiFi C++ 0.10.0 release

[Arpad Boda]

Thanks for bringing this up Ferenc, I'm +1.

On Mon, May 31, 2021 at 2:38 PM Ferenc Gerlits  wrote:

> Hi community,
>
> I'd like to initiate a discussion about the next release of MiNiFi C++.
> The
> last release was three months ago, and there have been many new features,
> bug fixes and stability improvements committed to the development branch
> since
> then.  I would be happy to take on RM duties for this release.
>
> New features since the 0.9.0 release:
> - new processors:
>* ListS3
>* PutAzureBlobStorage
>* ConsumeKafka
>* PerformanceDataMonitor
>* ConsumeJournald
> - add resource consumption data to heartbeats
> - build with Visual Studio 2019 on Windows.
>
> A few of the improvements and fixes:
> - revive SQL processors
> - fix expression language support in PublishKafka
> - implement FollowRedirects and SendBody properties in InvokeHTTP
> - add Initial Starting Position property to TailFile
> - support credential refresh in AWSCredentialsService
> - change default C2 protocol to REST
> - plus bug fixes, compiler warning fixes etc.
>
> I suggest we call this release 0.10.0 (rather than 1.0.0).  The code base
> is
> starting to stabilize and we're getting closer to a 1.0 milestone, but the
> extension API is not quite ready yet.  Staying on a 0.x release allows us
> more
> flexibility until we have an API we can commit to support in the long term.
>
> Do you agree it is time for a new release?  Are there any blockers that we
> should definitely include in this release?
>
> Thanks,
> Ferenc
>

Re: Jira contributor access

[Arpad Boda]

Rgr!

On Sun, Apr 25, 2021 at 3:23 PM Andres UPM  wrote:

> anmunoz
>

Re: JIRA contributor access

[Arpad Boda]

Granted, looking forward to your contribution!

On Tue, Mar 2, 2021 at 1:27 AM Eric Olson  wrote:

>  Oh, whoops, Jira user name is eaolson.
>
> On Monday, March 1, 2021, 3:15:35 AM CST, Arpad Boda 
> wrote:
>
>  Please subscribe to dev mailing list and provide your jira username!
>
> On Sat, Feb 27, 2021 at 12:50 AM Eric Olson 
> wrote:
>
> > I'd like to request JIRA contributor access
> >
>

Re: Jira contributor access

[Arpad Boda]

Arek,

Added you manually instead of using the rest API, should be good now.

On Mon, Mar 1, 2021 at 12:36 PM Arpad Boda  wrote:

> Should work immediately.
> Let me check and get back to you.
>
> On Mon, Mar 1, 2021 at 12:09 PM Arek Burdach 
> wrote:
>
>> Thanks for a quick response. I still can't e.g. assign issue to me. Does
>> it take some delay until I'll get such ability? I've tried to re-login
>> and it doesn't helped.
>>
>> Arek
>>
>> On 01.03.2021 10:14, Arpad Boda wrote:
>> > Arek,
>> >
>> > Granted, looking forward to your contribution!
>> >
>> > Cheers,
>> > Arpad
>> >
>> > On Sun, Feb 28, 2021 at 5:13 PM Arek Burdach 
>> wrote:
>> >
>> >> Hello,
>> >>
>> >> I would like to contribute to the nifi codebase. Please add me (Jira
>> >> username : arkadiusx)
>> >> as a contributor.
>> >>
>> >> Thanks
>> >> Arek
>> >>
>> >>
>>
>>

Re: Jira contributor access

[Arpad Boda]

Should work immediately.
Let me check and get back to you.

On Mon, Mar 1, 2021 at 12:09 PM Arek Burdach  wrote:

> Thanks for a quick response. I still can't e.g. assign issue to me. Does
> it take some delay until I'll get such ability? I've tried to re-login
> and it doesn't helped.
>
> Arek
>
> On 01.03.2021 10:14, Arpad Boda wrote:
> > Arek,
> >
> > Granted, looking forward to your contribution!
> >
> > Cheers,
> > Arpad
> >
> > On Sun, Feb 28, 2021 at 5:13 PM Arek Burdach 
> wrote:
> >
> >> Hello,
> >>
> >> I would like to contribute to the nifi codebase. Please add me (Jira
> >> username : arkadiusx)
> >> as a contributor.
> >>
> >> Thanks
> >> Arek
> >>
> >>
>
>

Re: JIRA contributor access

[Arpad Boda]

Please subscribe to dev mailing list and provide your jira username!

On Sat, Feb 27, 2021 at 12:50 AM Eric Olson 
wrote:

> I'd like to request JIRA contributor access
>

Re: Jira contributor access

[Arpad Boda]

Arek,

Granted, looking forward to your contribution!

Cheers,
Arpad

On Sun, Feb 28, 2021 at 5:13 PM Arek Burdach  wrote:

> Hello,
>
> I would like to contribute to the nifi codebase. Please add me (Jira
> username : arkadiusx)
> as a contributor.
>
> Thanks
> Arek
>
>

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

[Arpad Boda]

+1 (binding)
Verified build and signature.
Built on Debian 10 and Windows 10.
Executed tests, started agent with simple flow, verified C2 communication.
Verified commit and tag using Adam's script.

On Thu, Feb 25, 2021 at 7:47 AM Aldrin Piri  wrote:

> +1, binding
>
> comments:
> * verified hashes and signature
> * verified build and tests on Debian 10 and macOS 10.15
> * No strong issues with L 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=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: Release diff checker

[Arpad Boda]

+1, this is good stuff.
Should be added to the Nifi helper guide as well imho.

On Thu, Feb 25, 2021 at 10:00 AM Ádám Markovics 
wrote:

> Hi,
> Could I please get edit rights for the page?
> I assume this is it, I can't edit:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=173087303
> My user id is adam-markovics.
> Thanks,
>
> Ádám
>
> On Thu, Feb 25, 2021 at 4:48 AM Joe Witt  wrote:
> >
> > Adam,
> >
> > This is a good idea.  For now I recommend placing it or linking to it
> > from the release helper wiki page.
> >
> > Thanks
> >
> > On Tue, Feb 23, 2021 at 6:10 AM Ádám Markovics 
> wrote:
> > >
> > > Hi everyone,
> > > I have just created a release diff checker that works for NiFi and
> > > MiNiFi. Its purpose is to tell whether there is any difference between
> > > a release source package and a given tag in a given repo, by running a
> > > simple command in the command line.
> > > Motivation: there was a difference in the last MiNiFi RC, it was only
> > > spotted after many people have already approved. And this problem is
> > > highly automatizable.
> > > Code: https://github.com/adam-markovics/nifi-release-tools
> > > Please try it, I'm open to fixes and improvements.
> > > Could we even include it in official NiFi/MiNiFi repos?
> > > Regards,
> > >
> > > Ádám
>

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

[Arpad Boda]

+1 (binding)

Verified hashes and signature.
Built and executed tests both on Debian 10 and Win 10.
Started agent, connected to C2 server, designed simple flow.

Cheers,
Arpad

On Tue, Feb 16, 2021 at 4:57 PM Ferenc Gerlits
 wrote:

> +1 (non-binding)
>
> Verified hashes and the signature on the source bundle.  Suggestion: the
> format of the hash file could be changed to " *" so one
> can run eg. 'sha256 -c ...'.
> Built on (a Docker container running) Ubuntu 20.04, enabling everything
> except
> * TensorFlow, because I could not find an Ubuntu package for libtensorflow;
> * and JNI -- this built without error, but then I had to disable it because
> it caused a runtime error at startup.  I don't think this is a showstopper.
> Ran the binary using a simple InvokeHTTP -> LogAttribute flow yaml config;
> it worked as expected.
>
> Thanks,
> Ferenc
>
> On Tue, Feb 16, 2021 at 4:23 PM Adam Debreceni 
> wrote:
>
> > +1 (non-binding)
> >
> > Verified checksums and signatures.
> > Built on Windows 10 with kafka. Can connect to c2 server and receive
> > updates.
> > Can process windows event logs in various JSON formats and send them to
> > kafka
> > through SSL, in a multi broker setup.
> >
> > On Tue, Feb 16, 2021 at 9:50 AM Marton Szasz  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi MiNiFi C++ 0.9.0
> > >
> > > The source tarball, including signatures, digests, etc. can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.9.0/
> > >
> > > The Git tag is minifi-cpp-0.9.0
> > > The Git commit ID is a52faa5136031abfcc321a44fbcd954ee0f73764
> > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;a=commit;h=a52faa5136031abfcc321a44fbcd954ee0f73764
> > >
> > > Checksums of nifi-minifi-cpp-0.9.0-source.tar.gz:
> > > SHA256:
> 40fa837c86707e3bf0e8f0aca5bc279d813205cd326edf809e7785af7282
> > > SHA512:
> > >
> >
> 43490ba823d7846c3cc323a634d756a0a33828f5c82a623d19b77c4ddfe3248aa524245ee2c47a7fd04f41c3611758972307e221fa0a254e0aa5831c4f9b03f2
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/szaszm.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 200 issues were closed/resolved for this release:
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321520=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: Jira contributor access

[Arpad Boda]

Granted.

Looking forward to working with you!

On Sun, Feb 7, 2021 at 4:55 PM Lehel Boér  wrote:

> Hi,
>
> I'd like to contribute to NiFi. Could you please provide me JIRA access?
> My user name is: Lehel44.
>
> Kind Regards,
> Lehel Boér
>

Re: Contributor Access Request

[Arpad Boda]

Granted, looking forward to working with you!

On Fri, Feb 5, 2021 at 1:28 PM Timea Barna 
wrote:

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

Re: [DISCUSS] MiNiFi C++ 0.9.0 release

[Arpad Boda]

I think moving the tickets to 0.9.0 is easier, so +1 for 0.9.0!

On Thu, Jan 21, 2021 at 4:17 PM Joe Witt  wrote:

> Marton,
>
> I think if consensus matches your view on api stability then 0.9.0 is most
> appropriate over a 1.0 for now.  The progress made here in the past year is
> really awesome and frankly knowing some of the uses of this at the scale
> and diversity of usage is really exciting.
>
> You would just remove the 0.8.0 JIRA target and ensure any tickets tagged
> there are tagged to 0.9.0?  Or just go back to 0.8.0 and get rid of 0.9?
>
> Thanks
>
> On Thu, Jan 21, 2021 at 7:55 AM Marton Szasz  wrote:
>
> > Hi community,
> >
> > I'd like to initiate a discussion about the next release of MiNiFi C++.
> The
> > last release was over a year ago, and there have been countless new
> > features, bug fixes and stability improvements committed to the
> development
> > branch since then.
> >
> > Some highlights from the last year:
> > - Added support for RocksDB-based content repository for better
> performance
> > - Added SQL extension
> > - Improved task scheduling
> > - Various C2 improvements
> > - Bug fixes and improvements to TailFile, ConsumeWindowsEventLog,
> > MergeContent, CompressContent, PublishKafka, InvokeHTTP
> > - Implemented RetryFlowFile and smart handling of loopback connections
> > - Added a way to encrypt sensitive config properties and the flow
> > configuration
> > - Implemented full S3 support
> > - Reduced memory footprint when working with many flow files
> >
> > Why 0.9.0 instead of 0.8.0?
> > The codebase is starting to stabilize and we're getting closer to a 1.0
> > milestone, but I feel like the extension API is not yet something we can
> > commit to support in the long term. Additionally, a release branch for
> > 0.8.0 has been created earlier, but it was not released, and with all the
> > new development it wouldn't make sense to release it.
> >
> > Do you think 0.9.0 is a good target, or would you go with 0.8.0 or 1.0
> > instead? Are there any blockers that should definitely make it into the
> > next release?
> >
> > Thanks,
> > Marton
> >
>

Re: Jira contributor access

[Arpad Boda]

Christian,

Looking forward to your contribution! Granted.

Cheers,
Arpad

On Thu, Jan 7, 2021 at 4:54 PM 
wrote:

> Dear Nifi developers,
>
> we have started to use Nifi in the Swiss Federal Customs Administration
> and are really happy about its functionality and usability. We had to made
> a few tweaks here and there and I would like to start to contribute those
> patches back if they are of broader interest. Therefore, I would like to
> request contributor access to Nifi's JIRA for my username cgumpert.
>
> Thanks,
> Christian
>

Re: Jira contributor access

[Arpad Boda]

Hi Dan,

Granted, looking forward to your contribution!

Cheers,
Arpad

On Sat, Oct 10, 2020 at 7:17 PM Daniel Kim  wrote:

> Hello :)
>
> I was looking to request Jira contributor access.
> My Jira username is: deekim
>
> Thanks in advance.
>
> (Sorry if this a duplicate. I send out an email earlier in the week but
> wasn't sure if I did it right.)
>
>
> Best,
> - Dan
>

[ANNOUNCE] New Apache NiFi Committer Marton Szasz

[Arpad Boda]

Apache NiFi community,

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

Marton had more than 100 contributions to MiNiFi C++ this year in various
areas: from Windows-specific memory leaks to nice new features and a lot of
code reviews. He also showed active presence on the mailing list helping
out the community.

Welcome and congratulations!

Re: [VOTE] Release Apache NiFi Registry 0.7.0

[Arpad Boda]

+1 (binding)
Verified build on Java11, signatures, hashes. Lic and notice looks good.
Started, was able to create buckets and save flow.

On Sat, Jul 18, 2020 at 3:19 PM Tony Kurc  wrote:

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

[discuss]Release MiNiFi-CPP 0.8.0

[Arpad Boda]

Hey,

Quite a lot of time has passed since the last release and also a lot of
improvements and bug fixes have been made (Memleaks fixed, new threadpool,
some new processors, etc), so I think it's time for a new release.

Another important aspect would be the release of the current state of the
source before introducing some breaking changes - which seems to be
necessary at this point.

What do you think?

Thanks, regards,
Arpad

Re: [ANNOUNCE] Apache NiFi Registry 0.6.0 release

[Arpad Boda]

Michal,

Should be fixed, could you confirm?

May not all mirrors are synced, give it some time in case you still see the
old contents.

Thanks for letting us know!

Cheers,
Arpad

On Wed, Apr 8, 2020 at 10:55 AM Arpad Boda  wrote:

> Michal,
>
> Most probably you are right, will check and get back to you.
>
> On Wed, Apr 8, 2020 at 10:47 AM Michal Klempa 
> wrote:
>
>> Hi all,
>> the 'format' of sha256 file has changed (although it is still a valid
>> sha256 output). Haven't you experienced problems with Docker image build
>> with this?
>> See the change:
>> $ curl
>>
>> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-bin.tar.gz.sha256
>> e52d07e5689dbab5a04fa6afb4e89b316980daac781144c9651aa81a68c38068
>> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-bin.tar.gz.sha256e52d07e5689dbab5a04fa6afb4e89b316980daac781144c9651aa81a68c38068>
>>  ./nifi-registry-0.6.0-bin.tar.gz
>>
>> $ curl
>>
>> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha256
>> 6bf16eb1e73709b2723aaeccd7dddc08ff64ce7f46ef4ed2b0a36e24773b7f64
>> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha2566bf16eb1e73709b2723aaeccd7dddc08ff64ce7f46ef4ed2b0a36e24773b7f64>
>>
>> $ curl
>>
>> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.4.0/nifi-registry-0.4.0-bin.tar.gz.sha256
>> 7f19b19ba59ec0a9cc3428cab6c40e098143587bb23a837a6749a3b0b9e6167f
>> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.4.0/nifi-registry-0.4.0-bin.tar.gz.sha2567f19b19ba59ec0a9cc3428cab6c40e098143587bb23a837a6749a3b0b9e6167f>
>>
>> sha256sum by default outputs the   format, which is the
>> case for 0.6.0 release. Before this release, the official sha256 file had
>> the filename stripped.
>> It used to work with Dockerfile check
>>
>> https://github.com/apache/nifi-registry/blob/rel/nifi-registry-0.5.0/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile#L46
>>
>> I see you changed the Dockerbuild to something with maven? No more sha256
>> checks?
>> I will accommodate my builds.
>>
>> Best,
>> Michal
>>
>>
>> On Tue, Apr 7, 2020 at 4:12 PM Arpad Boda  wrote:
>>
>> > Hello
>> >
>> > The Apache NiFi team would like to announce the release of Apache NiFi
>> > Registry 0.6.0.
>> >
>> > Apache NiFi is an easy to use, powerful, and reliable system to process
>> and
>> > distribute data. Apache NiFi was made for dataflow. It supports highly
>> > configurable directed graphs of data routing, transformation, and system
>> > mediation logic.
>> >
>> > Registry, a subproject of Apache NiFi, is a complementary application
>> that
>> > provides a central location for storage and management of shared
>> resources
>> > across one or more instances of NiFi or MiNiFi.
>> >
>> > More details on Apache NiFi Registry, along with release artifacts, can
>> be
>> > found here:
>> > https://nifi.apache.org/registry.html
>> >
>> > Maven artifacts have been made available and mirrored as per normal ASF
>> > artifact processes.
>> >
>> > Issues closed/resolved for this list can be found here:
>> >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12347009
>> >
>> > Release note highlights can be found here:
>> >
>> >
>> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.0
>> >
>> > Thank you
>> > The Apache NiFi team
>> >
>>
>

Re: [ANNOUNCE] Apache NiFi Registry 0.6.0 release

[Arpad Boda]

Michal,

Most probably you are right, will check and get back to you.

On Wed, Apr 8, 2020 at 10:47 AM Michal Klempa 
wrote:

> Hi all,
> the 'format' of sha256 file has changed (although it is still a valid
> sha256 output). Haven't you experienced problems with Docker image build
> with this?
> See the change:
> $ curl
>
> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-bin.tar.gz.sha256
> e52d07e5689dbab5a04fa6afb4e89b316980daac781144c9651aa81a68c38068
> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-bin.tar.gz.sha256e52d07e5689dbab5a04fa6afb4e89b316980daac781144c9651aa81a68c38068>
>  ./nifi-registry-0.6.0-bin.tar.gz
>
> $ curl
>
> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha256
> 6bf16eb1e73709b2723aaeccd7dddc08ff64ce7f46ef4ed2b0a36e24773b7f64
> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.5.0/nifi-registry-0.5.0-bin.tar.gz.sha2566bf16eb1e73709b2723aaeccd7dddc08ff64ce7f46ef4ed2b0a36e24773b7f64>
>
> $ curl
>
> https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.4.0/nifi-registry-0.4.0-bin.tar.gz.sha256
> 7f19b19ba59ec0a9cc3428cab6c40e098143587bb23a837a6749a3b0b9e6167f
> <https://archive.apache.org/dist/nifi/nifi-registry/nifi-registry-0.4.0/nifi-registry-0.4.0-bin.tar.gz.sha2567f19b19ba59ec0a9cc3428cab6c40e098143587bb23a837a6749a3b0b9e6167f>
>
> sha256sum by default outputs the   format, which is the
> case for 0.6.0 release. Before this release, the official sha256 file had
> the filename stripped.
> It used to work with Dockerfile check
>
> https://github.com/apache/nifi-registry/blob/rel/nifi-registry-0.5.0/nifi-registry-core/nifi-registry-docker/dockerhub/Dockerfile#L46
>
> I see you changed the Dockerbuild to something with maven? No more sha256
> checks?
> I will accommodate my builds.
>
> Best,
> Michal
>
>
> On Tue, Apr 7, 2020 at 4:12 PM Arpad Boda  wrote:
>
> > Hello
> >
> > The Apache NiFi team would like to announce the release of Apache NiFi
> > Registry 0.6.0.
> >
> > Apache NiFi is an easy to use, powerful, and reliable system to process
> and
> > distribute data. Apache NiFi was made for dataflow. It supports highly
> > configurable directed graphs of data routing, transformation, and system
> > mediation logic.
> >
> > Registry, a subproject of Apache NiFi, is a complementary application
> that
> > provides a central location for storage and management of shared
> resources
> > across one or more instances of NiFi or MiNiFi.
> >
> > More details on Apache NiFi Registry, along with release artifacts, can
> be
> > found here:
> > https://nifi.apache.org/registry.html
> >
> > Maven artifacts have been made available and mirrored as per normal ASF
> > artifact processes.
> >
> > Issues closed/resolved for this list can be found here:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12347009
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.0
> >
> > Thank you
> > The Apache NiFi team
> >
>

[ANNOUNCE] Apache NiFi Registry 0.6.0 release

[Arpad Boda]

Hello

The Apache NiFi team would like to announce the release of Apache NiFi
Registry 0.6.0.

Apache NiFi is an easy to use, powerful, and reliable system to process and
distribute data. Apache NiFi was made for dataflow. It supports highly
configurable directed graphs of data routing, transformation, and system
mediation logic.

Registry, a subproject of Apache NiFi, is a complementary application that
provides a central location for storage and management of shared resources
across one or more instances of NiFi or MiNiFi.

More details on Apache NiFi Registry, along with release artifacts, can be
found here:
https://nifi.apache.org/registry.html

Maven artifacts have been made available and mirrored as per normal ASF
artifact processes.

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

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.6.0

Thank you
The Apache NiFi team

[Discuss]NiFi-registry 0.6.0 tagging and branching

[Arpad Boda]

Hi,

As you may know, 0.6.0 was technically a patch release, branching from
master based on 0.5.0 and cherry-picking non-breaking changes from master.

Because of this merging back the release branch to master would just cause
conflict and master has the proper versions (1.0.0) already set.

To avoid this issue I would just add the release tag to 0.6.0 branch and
avoid merging.

Please share your opinion, especially in case you have concerns with the
above.

Cheers,
Arpad

Re: [VOTE] Release Apache NiFi Registry 0.6.0

[Arpad Boda]

Apache NiFi Community,

I am pleased to announce that the nifi-registry-0.6.0 release of
Apache NiFi Registry passes with
  5 +1 (binding) votes
  5 +1 (non-binding) votes
   0 0 votes
   0 -1 votes

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
https://mail-archives.apache.org/mod_mbox/nifi-dev/202004.mbox/%3ccao4xokpfer_q5zluvsqwvwdvpzvboer+oe7r5zdwoqexfuu...@mail.gmail.com%3e

On Mon, Apr 6, 2020 at 12:20 AM Arpad Boda  wrote:

> +1 (non-binding)
>
> On Sun, Apr 5, 2020 at 8:44 PM Pierre Villard 
> wrote:
>
>> +1 (binding)
>>
>> Went trough the release helper, it looks good to me. Thanks for taking
>> care of this Arpad!
>>
>> Le ven. 3 avr. 2020 à 22:33, Tony Kurc  a écrit :
>>
>> > +1 (binding)
>> >
>> > Ran through the helper, compiled no problem, ran without issue, and
>> didn't
>> > see issues with licenses.
>> >
>> > 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=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: [VOTE] Release Apache NiFi Registry 0.6.0

[Arpad Boda]

+1 (non-binding)

On Sun, Apr 5, 2020 at 8:44 PM Pierre Villard 
wrote:

> +1 (binding)
>
> Went trough the release helper, it looks good to me. Thanks for taking
> care of this Arpad!
>
> Le ven. 3 avr. 2020 à 22:33, Tony Kurc  a écrit :
>
> > +1 (binding)
> >
> > Ran through the helper, compiled no problem, ran without issue, and
> didn't
> > see issues with licenses.
> >
> > 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=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: [VOTE] Release Apache NiFi Registry 0.6.0

[Arpad Boda]

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

[VOTE] Release Apache NiFi Registry 0.6.0

[Arpad Boda]

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

Apache NiFi Registry 0.6.0 RC1 Release Helper Guide

[Arpad Boda]

Hello Apache NiFi community,

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

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

# Import keys file:
gpg --import KEYS

# [optional] Clear out local maven artifact repository
# Pull down nifi-registry-0.6.0 source release artifacts for review:
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-source-release.zip
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-source-release.zip.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-source-release.zip.sha256
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.6.0/nifi-registry-0.6.0-source-release.zip.sha512

# Verify the signature
gpg --verify -v nifi-registry-0.6.0-source-release.zip.asc

# Verify the hashes (sha256, sha512) match the source and what was
provided in the vote email thread
shasum -a 256 nifi-registry-0.6.0-source-release.zip
shasum -a 512 nifi-registry-0.6.0-source-release.zip

# Unzip nifi-registry-0.6.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks
cd nifi-registry-0.6.0
mvn clean install -Pcontrib-check

# Optional - Verify integration tests pass against the supported databases
(requires Docker running)
mvn clean install -Pcontrib-check,integration-tests
-Dspring.profiles.active=postgres
mvn clean install -Pcontrib-check,integration-tests
-Dspring.profiles.active=mysql-56
mvn clean install -Pcontrib-check,integration-tests
-Dspring.profiles.active=mysql-57
mvn clean install -Pcontrib-check,integration-tests
-Dspring.profiles.active=mysql-8

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

# Verify the git commit ID is correct

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

# Look at the resulting convenience binary as found in
nifi-registry-assembly/target

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

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

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings. Thank you for your time and effort to validate the release!

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

[Arpad Boda]

+1 (non-binding)
Verified signature, checksum
Built, started.
Created a flow, sent and processed flowfiles via S2S.

On Tue, Feb 18, 2020 at 11:47 PM Joey Frazee 
wrote:

> +1 (non-binding)
> Verified checksums, signatures, and commit hash
> Ran build and all tests on OpenJDK 1.8.0_242 on Linux and OS X
> Created small cluster and ran some flows including load balancing
> On Feb 18, 2020, 12:28 PM -0800, Robert Fellows ,
> wrote:
> +1 (non-binding)
>
> * verified sigs and hashes
> * full build on java 11
> * tested a few processors, basic functionality.
>
> Thanks for RM'ing, Joe!
>
>
>
> On Tue, Feb 18, 2020 at 2:31 PM Matt Gilman 
> wrote:
>
> +1 (binding)
>
> - Check signatures and hashes
> - Full build
> - Verified some of the JIRAs addressed in this release
>
> Thanks for RMing Joe!
>
> On Tue, Feb 18, 2020 at 2:01 PM Matt Burgess  wrote:
>
> +1 (binding) ran through release helper and various flows. Thanks Joe
> for RM'ing!
>
> On Fri, Feb 14, 2020 at 10:15 PM Joe Witt  wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi
> 1.11.2.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1157
>
> The source being voted upon and the convenience binaries can be found
> at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.2/
>
> A helpful reminder on how the release candidate verification process
> works:
>
>
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.11.2-RC1
> The Git commit ID is 6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
>
>
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
>
> Checksums of nifi-1.11.2-source-release.zip:
> SHA256:
> 2a030956a7cc9578e616195dd4cf8a853976e17eb040a7b216f844ae2ce9a610
> SHA512:
>
>
>
> 135101f3f9b37b559e850e79c89bad36d707126fcea559fa4f6846c4cb21c17ab51c119c5005df359a4d3a066c66611b00816c2f7586b24d34f0f418d4b5c527
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 14 issues were closed/resolved for this release:
>
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12346972
>
> Release note highlights can be found here:
>
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.2
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.11.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>
>
>
>
> --
> ---
> Rob Fellows
>

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

[Arpad Boda]

+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=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...
>

[Discuss] Release Nifi Registry 0.6.0

[Arpad Boda]

Hi Team,

As NiFi already compiles and runs on Java 11 I was wondering about a
Registry patch release (based on 0.5.0) that comes with Java 11 support.

The motivation behind is Java 8 getting less and less supported (for eg.
there is no official stable package for Debian 10) so we could run
everything on Java 11.

I'll volunteer  to RM this.

In case you are aware of any commits that worth to be considered for such
minor release (for eg.: security),  please let us know!

Thanks,
Arpad

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

[Arpad Boda]

+1

   - Verified signature, checksums.
   - Built properly.
   - Started NiFi, sent flowfiles from MiNiFi, designed flow to handle
   them.


Created https://issues.apache.org/jira/browse/NIFI-7049 in the meanwhile as:

   - SFTP tests can fail on "clean" hosts
   - The underlying behavior seems to be unintentional and error-prone


I don't consider it as a blocker as it has been working this way for quite
a while.


On Tue, Jan 21, 2020 at 1:33 AM Andy LoPresto  wrote:

> +1, binding.
>
> Verified normal signatures and checksums, deployed instance, and verified
> selected Jiras were included in the build.
>
> Pierre, I opened NIFI-7048 to resolve the issue you documented below.
> Thanks.
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> > On Jan 20, 2020, at 11:33 AM, Pierre Villard <
> pierre.villard...@gmail.com> wrote:
> >
> > +1 (binding) release this package as nifi-1.11.0
> >
> > Went through the usual check process. Also deployed a 3-nodes secured
> > cluster with OIDC behind a load balancer with Terraform on Google Cloud.
> > Tested various flows. It looks good to me.
> >
> > Some notes - I did run into a test failure (that I didn't have before)
> but
> > it was because JAVA_HOME was not set properly. I copy the error in case
> it
> > happens to someone else. This is on recently added tests:
> >
> > [ERROR] Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed:
> > 0.666 s <<< FAILURE! - in org.apache.nifi.io.socket.SSLContextFactoryTest
> > [ERROR]
> >
> testShouldVerifyKeystoreWithEmptyKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.051 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithEmptyKeyPassword(SSLContextFactoryTest.groovy:162)
> > [ERROR]
> >
> testShouldVerifyKeystoreWithDifferentKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.002 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithDifferentKeyPassword(SSLContextFactoryTest.groovy:138)
> > [ERROR]
> >
> testShouldVerifyKeystoreWithSameKeyPassword(org.apache.nifi.io.socket.SSLContextFactoryTest)
> > Time elapsed: 0.001 s  <<< ERROR!
> > java.io.FileNotFoundException: null/jre/lib/security/cacerts (No such
> file
> > or directory)
> > at
> >
> org.apache.nifi.io.socket.SSLContextFactoryTest.testShouldVerifyKeystoreWithSameKeyPassword(SSLContextFactoryTest.groovy:113)
> >
> > Also, during the build, I spotted an ERROR message (that does not prevent
> > the completion of the build). We might want to solve this for the next
> > release:
> >  [INFO] --- frontend-maven-plugin:1.4:npm (npm install) @
> > nifi-jolt-transform-json-ui ---
> >  [INFO] Running 'npm --cache-min Infinity install' in
> >
> /Users/pierrevillard/tmp/nifi-1.11.0/nifi-nar-bundles/nifi-standard-bundle/nifi-jolt-transform-json-ui/target/frontend-working-directory
> >  [WARNING] npm WARN deprecated angular-ui-router@0.2.18: This npm
> package
> > 'angular-ui-router' has been renamed to '@uirouter/angularjs'. Please
> > update your package.json. See
> > https://ui-router.github.io/blog/uirouter-scoped-packages/
> >  [ERROR] npm notice created a lockfile as package-lock.json. You should
> > commit this file.
> >  [WARNING] npm WARN nifi-jolt-transform-json-ui@ No license field.
> >  [ERROR]
> >
> > Thanks for taking care of the release Joe!
> >
> > Le lun. 20 janv. 2020 à 03:21, Joe Witt  a écrit :
> >
> >> 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:
> >> 

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

[Arpad Boda]

+1

Verified signature and hashes
Built and tests passed
NiFi started, created a simple flow
Transferred flowfiles using raw S2S

All worked perfectly

On Fri, Jan 17, 2020 at 2:58 PM Shawn Weeks 
wrote:

> +1 Build runs fine and hashes match.
>
> On 1/16/20, 4:54 PM, "Joe Witt"  wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi
> nifi-1.11.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1153
>
> The source being voted upon and the convenience binaries can be found
> at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.0/
>
> The Git tag is nifi-1.11.0-RC2
> The Git commit ID is 97bec7ad0f1efe3e28ac9cb7d2364134727cd07b
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=97bec7ad0f1efe3e28ac9cb7d2364134727cd07b
>
> Checksums of nifi-1.11.0-source-release.zip:
> SHA256:
> f43245e21dba63061a7f5bc8e2590f1242112380083791acff10a07ecf357234
> SHA512:
>
> 4634981608af35b76a96375e84660fbb75148e67ab1d0b6c192ee01eeb7c9a4cb1ebd7671ad73fa27a8e9bb71f361e32f49214573be5564d781612316cc8f88f
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 112 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=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...
>
>
>

[ANNOUNCE] Apache NiFi MiNiFi C++ 0.7.0 release

[Arpad Boda]

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

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

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

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

Highlights of 0.7.0 release include:

   - Added several processors (OPC, SFTP and OpenCV to name a few )
   - Added Windows specific processors (ConsumeEventLog for eg.)
   - Improved Windows support (SiteToSite, processor features, OpenSSL
support)
   - Improved performance (related to usage of repositories)
   - Windows build made trivial
   - Fixed many issues including some security vulnerabilities

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

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

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

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

Thank you
The Apache NiFi team

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

[Arpad Boda]

Apache NiFi Community,

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

Thanks to all who helped make this release possible.

Here is the PMC vote thread:
http://apache-nifi.1125220.n5.nabble.com/VOTE-Release-Apache-NiFi-MiNiFi-C-0-7-0-RC1-td29724.html

On Sat, Jan 11, 2020 at 6:30 PM Arpad Boda  wrote:

> +1 - verified build, checksums and execution on Debian.
>
> Thanks all for the documentation improvements, will adjust helper and
> readme accordingly!
>
> On Sat, Jan 11, 2020 at 3:57 AM Andy LoPresto 
> wrote:
>
>> +1 (binding)
>>
>> I encountered a number of obstacles during this validation, some of which
>> are definitely because I haven’t worked on the C++ effort (or even built
>> it) in at least 6 months. These are not complaints, just wrinkles I
>> captured so we can improve this process for next time. Noted here for
>> posterity:
>>
>> * The SHA-512 digest I calculated locally matched the email, but the
>> .sha512 files are not published in the hosted server for any artifacts.
>> * The GPG verification command in the helper email should include -v to
>> show the underlying digest algorithm used
>> * The wget commands have newlines inserted, which means they cannot be
>> copied/pasted into the terminal without manual modification
>> * The README section on bootstrapping helped immensely, but is not
>> perfectly aligned with the current process
>> * The wording of “disable tests…..disabled” is unclear (in this case it
>> means that the tests will be run)
>> * The bootstrap instructions are missing the directive to change into the
>> build/ directory before running make (directory in example prompt is wrong)
>> * The bootstrap instructions are missing the directive to untar the
>> binary artifact and change into that directory before running
>> ./bin/minifi.sh start
>> * A sample flow (config.yml) with a GenerateFlowFile and LogAtttribute
>> flow would be helpful to allow people to verify the successful install of
>> MiNiFi without going through the full flow design in NiFi, export template,
>> convert template process
>>
>> All in all, a lot of great work done on this release. Thanks Arpad.
>>
>>
>> Andy LoPresto
>> alopre...@apache.org
>> alopresto.apa...@gmail.com
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>>
>> > On Jan 10, 2020, at 12:55 PM, Matt Gilman 
>> wrote:
>> >
>> > +1 (binding)
>> >
>> > Ran through release helper. Verified signature, checksums, build, tests,
>> > etc. Looks good.
>> >
>> > Thanks for RMing Arpad!
>> >
>> > On Fri, Jan 10, 2020 at 3:39 PM Kevin Doran 
>> wrote:
>> >
>> >> +1 (binding)
>> >>
>> >> Ran through the steps in the release helper guide. Noticed a few
>> >> release helper instructions that can be improved for next time (no
>> >> mention of bootstrap.sh),
>> >> but was able to figure it out by using the README file included in the
>> >> source release.
>> >>
>> >> Hashes & sig all looked good. Was able to build, including the docker
>> >> image. Tests
>> >> all passed. Tested integration with a NiFi cluster with the 0.7.0
>> >> minifi sending flow files over s2s and everything worked as expected.
>> >>
>> >> Overall, seems to be a very solid, polished release. Nice work all!
>> >>
>> >> On Fri, Jan 10, 2020 at 3:35 PM Joe Witt  wrote:
>> >>>
>> >>> +1 (binding)
>> >>>
>> >>> Comments
>> >>> - Notice file copyright year needs to be 2020
>> >>> - I did not enable python support but I get the minifi-python dir
>> anyway
>> >>> and log entry on startup such as
>> >>>   Caught Exception ModuleNotFoundError: No module named 'google'
>> >>>
>> >>> Great progress with this release!  Nice work.  Building and running
>> tests
>> >>> was easier than I ever remember.
>> >>>
>> >>> Thanks
>> >>>
>> >>> On Fri, Jan 10, 2020 at 8:27 AM Dániel Bakai > >
>> >>> wrote:
>> >>>
>> >>>> +1, non-binding
>> >>>>
>> >>>> Verifications performed:
>> >>>>
>> >>>> SHA256 checksums downloaded: OK
>> >>>> SHA512 checksum of nif

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

[Arpad Boda]

consistently fail when ran in parallel,
> running
> >>>> them sequentially works, otherwise OK
> >>>> centos:7 docker container: had to install 'zlib-devel' and 'which',
> >>>> otherwise OK
> >>>> debian:stretch docker container: OK
> >>>> fedora:29 docker container: had to install 'zlib-devel' and 'which',
> >>>> otherwise OK
> >>>> ubuntu:xenial docker container: had to install 'tzdata' package for
> >>>> ExpressionLanguageTest to work, otherwise OK
> >>>>
> >>>> Run appropriate convenience binary with a GenerateFlowFile ->
> >> LogAttribute
> >>>> flow:
> >>>> macOS 10.14.6: OK
> >>>> ubuntu:bionic docker container: OK
> >>>> centos:7 docker container: OK
> >>>> debian:stretch docker container: OK
> >>>> fedora:29 docker container: OK
> >>>> ubuntu:xenial docker container: OK
> >>>> General note: there is a dynamic libpython dependency in most *nix
> >>>> convenience binaries, requiring manual installation from the native
> >> repos,
> >>>> in the case of CentOS 7 from EPEL.
> >>>>
> >>>> win_build_vs.bat build /64 /K /P && ctest -C Release && run package
> >> with a
> >>>> GenerateFlowFile -> LogAttribute flow:
> >>>> Windows 10: TailFileTests failed, but this is, as far as I know, a
> >> known
> >>>> issue, otherwise OK
> >>>>
> >>>> Install convenience msi on a completely clean Windows VM and run with
> a
> >>>> GenerateFlowFile -> LogAttribute flow both as a service and from
> >> cmd.exe:
> >>>> Windows 7: OK
> >>>> Windows 10: OK
> >>>>
> >>>>
> >>>> I think this release brings great improvements over 0.6.0.
> >>>>
> >>>> On Fri, 10 Jan 2020 at 02:32, Aldrin Piri 
> >> wrote:
> >>>>
> >>>>> +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=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: Supporting C++ port of Apache MiNiFi, on RISC-V

[Arpad Boda]

Ivan,

First of all, welcome and happy to see contribution!

Not sure I properly understand the co-referencing issue, could you be a bit
more specific?

What would you like to achieve with MiNiFi on this stack?

Cheers,
Arpad

On Fri, Jan 10, 2020 at 2:00 PM Ivan Serdyuk 
wrote:

> Informing about recent attempts to bootstrap:
>
> https://github.com/hex-five/multizone-secure-iot-stack/issues/67
> https://issues.apache.org/jira/browse/MINIFICPP-1112
> .
>
> It is not properly co-referenced, between github and Jira (not yet). That
> should be fixed - and I am not familiar with project maintenance strategy.
>
> CC'ing to member of the PULP team and Cesare Garlati.
>
> Ivan
>

Apache MiNiFi C++ 0.7.0 RC1 Release Helper Guide

[Arpad Boda]

Hello Apache NiFi community,

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

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

# Import keys file:
gpg --import KEYS

# Pull down nifi-${NIFI_VERSION} source release artifacts for review:
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-0.7.0-source.tar.gz
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-0.7.0-source.tar.gz.asc
wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.7.0/nifi-minifi-cpp-0.7.0-source.tar.gz.sha256

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

# Verify the hashes (sha256, sha512) match the source and what was provided
in the vote email thread
shasum -a 256 nifi-minifi-cpp-0.7.0-source.tar.gz
shasum -a 512 nifi-minifi-cpp-0.7.0-source.tar.gz

#untar the source
tar -zxvf nifi-minifi-cpp-0.7.0-source.tar.gz

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

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

# Verify the git commit ID is correct

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

# Look at the resulting convenience binary as found in

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

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

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

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

[VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)

[Arpad Boda]

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=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: [DISCUSS] Apache NiFi MiNiFi C++ 0.6.1

[Arpad Boda]

As the resolution of MINIFICPP-960 took quite a while and further issues
popped up that raised concerns, 0.6.1 efforts were abandoned.

0.6.1 was meant to be mostly Windows-focused, although a lot of Windows
related fixes/improvements have been added since and also other major
performance improvements and fixes have been done, so I would recommend
every MiNiFi-cpp user to wait for 0.7.0, which is planned to be released in
a few weeks.

Let me know if you have concerns/questions.

Regards,
Arpad


On Wed, Jul 10, 2019 at 10:08 AM Daniel Bakai 
wrote:

> I agree, I would not be comfortable with releasing a fix until it is
> properly
> tested, because there might well be other issues.
>
> On Tue, 9 Jul 2019 at 18:54, Marc Parisi  wrote:
>
> > Good find! I'm +1 on adding that fix piggy backed on the aforementioned
> > test ticket. There are almost no tests on listen http and it has been a
> > risk for some time.
> >
> > I'd like to avoid adding any fixes without those tests in 814 ( we'll end
> > up fixing in master and cherry picking). Happy to help as time allows
> but I
> > think this bug has been around long enough that we can suffer the time to
> > add those tests if we want it fixed in 0.6.1
> >
> > On Tue, Jul 9, 2019, 12:24 PM Daniel Bakai 
> > wrote:
> >
> > > Hi,
> > >
> > > I am working on https://issues.apache.org/jira/browse/MINIFICPP-814,
> > > and unfortunately https support in ListenHTTP seems to be broken since
> > > https://github.com/apache/nifi-minifi-cpp/pull/394 was merged, which
> > > disabled SSL support in civetweb.
> > > This unfortunately means that it is broken in 0.6.0 as well as on
> master.
> > > I have verified this with the macOS binary release of 0.6.0.
> > > I propose we discuss whether the fix for this (once, hopefully soon,
> > ready)
> > > be added to 0.6.1 as
> https://issues.apache.org/jira/browse/MINIFICPP-960
> > >
> > > Best,
> > > Daniel
> > >
> > > On Sat, 6 Jul 2019 at 17:21, Arpad Boda  wrote:
> > >
> > > > As a result of this vote MiNiFi C++ 0.6.1 is going to be released
> soon
> > > with
> > > > the following scope:
> > > > https://issues.apache.org/jira/browse/MINIFICPP-786
> > > > https://issues.apache.org/jira/browse/MINIFICPP-933
> > > > https://issues.apache.org/jira/browse/MINIFICPP-919
> > > >
> > > > I will do the RM duties.
> > > >
> > > > Regards,
> > > > Arpad
> > > >
> > > > On Thu, Jun 27, 2019 at 3:00 PM Aldrin Piri 
> > > wrote:
> > > >
> > > > > I agree with 786 for sure.  I apologize, I may have interpreted
> your
> > > > > initial response a bit literally with regards to the "feature
> > bearing"
> > > > > JIRAs.  Just wanted to clarify that new features would not be in
> > scope
> > > > for
> > > > > a fix version release, but in terms of adjusting the expected
> > > > > functionality, totally onboard with that.
> > > > >
> > > > > On Thu, Jun 27, 2019 at 8:47 AM Jeremy Dyer 
> > wrote:
> > > > >
> > > > > > Completely agree but isn’t MINIFICPP-786 an issue we could
> include
> > as
> > > > > part
> > > > > > of that?
> > > > > >
> > > > > > On Wed, Jun 26, 2019 at 6:35 PM Aldrin Piri <
> aldrinp...@gmail.com>
> > > > > 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 <
> ab...@apache.org>
> > > > > wrote:
> > > > > > > >>
> > > > > > > >> Happy to take RM roles as well.
> > > > > > > >>
> > > > > > > >>> On Wed, Jun 26, 2019 at 10:30 AM Arpad Boda <
> > > ab..

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

[Arpad Boda]

I think there are more of these:
https://issues.apache.org/jira/browse/NIFI-5750

On Wed, Aug 7, 2019 at 7:54 AM Marc Pellmann  wrote:

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

Re: [DISCUSS] Predictive Analytics for NiFi Metrics

[Arpad Boda]

If you could share a bit more details about your OPC and Modbus usage, that
would be highly appreciated!

On Wed, Jul 31, 2019 at 12:01 PM Craig Knell  wrote:

> Sounds. Great
>
> Let me know if you need some help
>
> Best regards
>
> Craig
>
>
>
> > On 31 Jul 2019, at 17:31, Arpad Boda  wrote:
> >
> > Craig,
> >
> > OPC ( https://issues.apache.org/jira/browse/MINIFICPP-819 ) and Modbus (
> > https://issues.apache.org/jira/browse/MINIFICPP-897 ) are on the way for
> > MiNiFi c++, hopefully both will be part of next release (0.7.0).
> > It's gonna be legen... wait for it! :)
> >
> > Regards,
> > Arpad
> >
> >> On Wed, Jul 31, 2019 at 2:30 AM Craig Knell 
> wrote:
> >>
> >> Hi Folks
> >>
> >> That's our use case now.  All our Models are run in python.
> >> Currently we send events to the ML via http, although this is not
> optimal
> >>
> >> Our use case is edge ML where we want a light weight wrapper for
> >> Python code base.
> >> Jython however does not work with the code base
> >> I'm think of changing the interface to some thing like REDIS for pub/sub
> >> Id also like this to be a push deployment via minifi
> >>
> >> Also support for sensors via protocols via Modbus and OPC would be great
> >>
> >> Craig
> >>
> >>> On Wed, Jul 31, 2019 at 1:43 AM Joe Witt  wrote:
> >>>
> >>> Definitely something that I think would really help the community.  It
> >>> might make sense to frame/structure these APIs such that an internal
> >> option
> >>> could be available to reduce dependencies and get up and running but
> that
> >>> also just as easily a remote implementation where the engine lives and
> is
> >>> managed externally could also be supported.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> On Tue, Jul 30, 2019 at 1:40 PM Andy LoPresto 
> >> wrote:
> >>>
> >>>> Yolanda,
> >>>>
> >>>> I think this sounds like a great idea and will be very useful to
> >>>> admins/users, as well as enabling some interesting next-level
> >> functionality
> >>>> and insight generation. Thanks for putting this out there.
> >>>>
> >>>> Andy LoPresto
> >>>> alopre...@apache.org
> >>>> alopresto.apa...@gmail.com
> >>>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >>>>
> >>>>> On Jul 30, 2019, at 5:55 AM, Yolanda Davis <
> >> yolanda.m.da...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>> Hello Everyone,
> >>>>>
> >>>>> I wanted to reach out to the community to discuss potentially
> >> enhancing
> >>>>> NiFi to include predictive analytics that can help users assess and
> >>>> predict
> >>>>> NiFi behavior and performance. Currently NiFi has lots of metrics
> >>>> available
> >>>>> for areas including jvm and flow component usage (via component
> >> status)
> >>>> as
> >>>>> well as provenance data which NiFi makes available either through
> >> the UI
> >>>> or
> >>>>> reporting tasks (for consumption by other systems). Past discussions
> >> in
> >>>> the
> >>>>> community cite users shipping this data to applications such as
> >>>> Prometheus,
> >>>>> ELK stacks, or Ambari metrics for further analysis in order to
> >>>>> capture/review performance issues, detect anomalies, and send alerts
> >> or
> >>>>> notifications.  These systems are efficient in capturing and helping
> >> to
> >>>>> analyze these metrics however it requires customization work and
> >>>> knowledge
> >>>>> of NiFi operations to provide meaningful analytics within a flow
> >> context.
> >>>>>
> >>>>> In speaking with Matt Burgess and Andy Christianson on this topic we
> >> feel
> >>>>> that there is an opportunity to introduce an analytics framework that
> >>>> could
> >>>>> provide users reasonable predictions on key performance indicators
> >> for
> >>>>> flows, such as back pressure and flow rate, to help administrators
> >>>> improve
>

Re: [DISCUSS] Predictive Analytics for NiFi Metrics

[Arpad Boda]

Craig,

OPC ( https://issues.apache.org/jira/browse/MINIFICPP-819 ) and Modbus (
https://issues.apache.org/jira/browse/MINIFICPP-897 ) are on the way for
MiNiFi c++, hopefully both will be part of next release (0.7.0).
It's gonna be legen... wait for it! :)

Regards,
Arpad

On Wed, Jul 31, 2019 at 2:30 AM Craig Knell  wrote:

> Hi Folks
>
> That's our use case now.  All our Models are run in python.
> Currently we send events to the ML via http, although this is not optimal
>
> Our use case is edge ML where we want a light weight wrapper for
> Python code base.
> Jython however does not work with the code base
> I'm think of changing the interface to some thing like REDIS for pub/sub
> Id also like this to be a push deployment via minifi
>
> Also support for sensors via protocols via Modbus and OPC would be great
>
> Craig
>
> On Wed, Jul 31, 2019 at 1:43 AM Joe Witt  wrote:
> >
> > Definitely something that I think would really help the community.  It
> > might make sense to frame/structure these APIs such that an internal
> option
> > could be available to reduce dependencies and get up and running but that
> > also just as easily a remote implementation where the engine lives and is
> > managed externally could also be supported.
> >
> > Thanks
> >
> >
> > On Tue, Jul 30, 2019 at 1:40 PM Andy LoPresto 
> wrote:
> >
> > > Yolanda,
> > >
> > > I think this sounds like a great idea and will be very useful to
> > > admins/users, as well as enabling some interesting next-level
> functionality
> > > and insight generation. Thanks for putting this out there.
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > > On Jul 30, 2019, at 5:55 AM, Yolanda Davis <
> yolanda.m.da...@gmail.com>
> > > wrote:
> > > >
> > > > Hello Everyone,
> > > >
> > > > I wanted to reach out to the community to discuss potentially
> enhancing
> > > > NiFi to include predictive analytics that can help users assess and
> > > predict
> > > > NiFi behavior and performance. Currently NiFi has lots of metrics
> > > available
> > > > for areas including jvm and flow component usage (via component
> status)
> > > as
> > > > well as provenance data which NiFi makes available either through
> the UI
> > > or
> > > > reporting tasks (for consumption by other systems). Past discussions
> in
> > > the
> > > > community cite users shipping this data to applications such as
> > > Prometheus,
> > > > ELK stacks, or Ambari metrics for further analysis in order to
> > > > capture/review performance issues, detect anomalies, and send alerts
> or
> > > > notifications.  These systems are efficient in capturing and helping
> to
> > > > analyze these metrics however it requires customization work and
> > > knowledge
> > > > of NiFi operations to provide meaningful analytics within a flow
> context.
> > > >
> > > > In speaking with Matt Burgess and Andy Christianson on this topic we
> feel
> > > > that there is an opportunity to introduce an analytics framework that
> > > could
> > > > provide users reasonable predictions on key performance indicators
> for
> > > > flows, such as back pressure and flow rate, to help administrators
> > > improve
> > > > operational management of NiFi clusters.  This framework could offer
> > > > several key features:
> > > >
> > > >   - Provide a flexible internal analytics engine and model api which
> > > >   supports the addition of or enhancement to onboard models
> > > >   - Support integration of remote or cloud based ML models
> > > >   - Support both traditional and online (incremental) learning
> methods
> > > >   - Provide support for model caching  (perhaps later inclusion into
> a
> > > >   model repository or registry)
> > > >   - UI enhancements to display prediction information either in
> existing
> > > >   summary data, new data visualizations, or directly within the
> > > flow/canvas
> > > >   (where applicable)
> > > >
> > > > For an initial target we thought that back pressure prediction would
> be a
> > > > good starting point for this initiative, given that back pressure
> > > detection
> > > > is a key indicator of flow performance and many of the metrics
> currently
> > > > available would provide enough data points to create a reasonable
> > > > performing model.  We have some ideas on how this could be achieved
> > > however
> > > > we wanted to discuss this more with the community to get thoughts
> about
> > > > tackling this work, especially if there are specific use cases or
> other
> > > > factors that should be considered.
> > > >
> > > > Looking forward to everyone's thoughts and input.
> > > >
> > > > Thanks,
> > > >
> > > > -yolanda
> > > >
> > > > --
> > > > yolanda.m.da...@gmail.com
> > > > @YolandaMDavis
> > >
> > >
>
>
>
> --
> Regards
>
> Craig Knell
> Mobile: +61 402 128 615
> Skype: craigknell
>

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

[Arpad Boda]

As a result of this vote MiNiFi C++ 0.6.1 is going to be released soon with
the following scope:
https://issues.apache.org/jira/browse/MINIFICPP-786
https://issues.apache.org/jira/browse/MINIFICPP-933
https://issues.apache.org/jira/browse/MINIFICPP-919

I will do the RM duties.

Regards,
Arpad

On Thu, Jun 27, 2019 at 3:00 PM Aldrin Piri  wrote:

> I agree with 786 for sure.  I apologize, I may have interpreted your
> initial response a bit literally with regards to the "feature bearing"
> JIRAs.  Just wanted to clarify that new features would not be in scope for
> a fix version release, but in terms of adjusting the expected
> functionality, totally onboard with that.
>
> On Thu, Jun 27, 2019 at 8:47 AM Jeremy Dyer  wrote:
>
> > Completely agree but isn’t MINIFICPP-786 an issue we could include as
> part
> > of that?
> >
> > On Wed, Jun 26, 2019 at 6:35 PM Aldrin Piri 
> wrote:
> >
> > > I think the intent is for this to be a fix release and wouldn’t include
> > > any new features.
> > >
> > > > On Jun 26, 2019, at 17:47, Jeremy Dyer  wrote:
> > > >
> > > > +1 it’s time and lots of feature bearing JIRAs have been resolved
> > > >
> > > > I do agree with with Arpad however on the inclusion of MINIFICPP-786
> > > >
> > > >> On Wed, Jun 26, 2019 at 5:37 PM Arpad Boda 
> wrote:
> > > >>
> > > >> Happy to take RM roles as well.
> > > >>
> > > >>> On Wed, Jun 26, 2019 at 10:30 AM Arpad Boda 
> > > 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: nifi

[Arpad Boda]

"nye fye" (nī fī) is the preferred pronunciation.

https://nifi.apache.org/faq.html



On Fri, Jul 5, 2019 at 1:43 PM 鹿骏 <405453...@qq.com> wrote:

> sorry to trouble you.
> I'm curious about how to pronounce ‘nifi’?

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

[Arpad Boda]

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

[Arpad Boda]

+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: Support for JDK 11

[Arpad Boda]

Please follow the this Jira: https://issues.apache.org/jira/browse/NIFI-5174

On Mon, Jun 17, 2019 at 2:59 PM nifi4ad  wrote:

> Hi Mike,
>
> This post if from March, I was wondering if JDK 11 compatible package is
> available now for NIFI. Is NIFI 1.9.2 is JDK11 compatible ?
>
>
>
> --
> Sent from: http://apache-nifi-developer-list.39713.n7.nabble.com/
>

Re: NIFI-6150

[Arpad Boda]

Ryan,

Let me ask about a prerequisite: why do you think 1.9.2 is going to be released 
at all? __

I think the next release is going to be 1.10 unless some serious degradation is 
found in 1.9.1

Regards,
Arpad

On 27/03/2019, 15:47, "Ryan Ward"  wrote:

I just came across NIFI-6150 and was wondering if there are plans to
release 1.9.2?

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

[Arpad Boda]

+1



-Verified checksums, signature, commit ID

-Built on Ubuntu 16 and OS X 10.13 (executed all tests on both systems)

-Verified MiNiFi and some Nanofi examples to start and work as expected

-LICENSE found a looks good to me

-NOTICE found, but should be updated:

Apache NiFi MiNiFi

Copyright 2017 The Apache Software Foundation

-README.md found a looks good to me, contains a minor typo for Bionic:

| Ubuntu 16  | make u18 | nifi-minifi-cpp-bionic-$VERSION-bin.tar.gz





On 19/03/2019, 20:59, "Aldrin Piri"  wrote:



+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=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)

[Arpad Boda]

+1

-Verified signature
-Verified checksum
-Built, executed tests
-Created a simple flow
-Sent flow files both using raw and HTTP S2S, verified them.

On 13/03/2019, 22:24, "Rob Fellows"  wrote:

+1

Went through the Release Helper Guide.
Started the app and created a simple data flow. It seemed good to me.

Thanks,
Rob

On Wed, Mar 13, 2019 at 3:16 PM Mark Payne  wrote:

> +1 (binding)
>
> Verified signature, hashes. Build succeeded with contrib-check and grpc
> profiles.
> Started app and performed some basic functionality testing and all seemed
> correct.
>
> Thanks
> -Mark
>
> > On Mar 13, 2019, at 1:49 AM, 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=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...
>
>

-- 
Thanks,
Rob Fellows

Re: Opinions on Assembly target location

[Arpad Boda]

Hi,

In my opinion, there is another question here to be answered: what version of 
NiFi NARs do we expect to work in MiNiFi?

I see two different approaches here:
-#1) MiNiFi is compatible with a given NiFi version, like 1.9.0, NARs in that 
release work properly in MiNiFi.
In this case the tests belong to MiNiFi and NiFi there becomes a dependency -> 
the tests are required to pass when upgrading the dependency.
-#2) MiNiFi is compatible with master. This means that whatever we introduce in 
NiFi shouldn't break, so the tests more belong to NiFi.

According to my experience preventing the merge of a breaking change is easier 
than fixing later, which would make me vote for #2, however this approach has a 
side effect, too: introducing a breaking change (that MiNiFi needs to adapt) 
becomes a huge pain, it's much easier in #1. 

Regards,
Arpad

On 27/02/2019, 17:44, "Marc Parisi"  wrote:

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

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

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

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

TL;DR:  Where feature Live?

Any insight/opinions are appreciated. Thanks!

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

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

[Arpad Boda]

+1

All the below passed successfully:
-Signature verified
-Checksums verified
-Build and tests executed properly
-Started a new instance
-Created a simple flow
-Transmitted flow files from MiNiFi via http 
-Transmitted flow files from MiNiFi via raw 

Regards,
Arpad

On 17/02/2019, 04:50, "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=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: SSD fatigue

[Arpad Boda]

Just some details to add here:
-Make sure TRIM is enabled, it extends lifetime of your SSDs.
-The reason larger SSDs tend to last longer is simple: firmware load-balances 
usage between cells, higher capacity means more cells -> less frequent data 
modification in one cell. 
-As Michael mentioned, SSDs are different. I would suggest checking the 
differences between SLC, MLC and TLC and I personally wouldn't recommend TLC 
SSDs for such usage. SLCs tend to be tremendously expensive, so go for MLC. 

I've found this article about the lifetime of SSDs:
https://techreport.com/review/26523/the-ssd-endurance-experiment-casualties-on-the-way-to-a-petabyte

It seems that even the less endurable ones lasted for at least 500TBs of data 
written, which - in my opinion - is more than enough. 

Regards,
Arpad

On 14/12/2018, 23:01, "Michael Moser"  wrote:

Hello Phil,

When supporting an I/O intensive application such as NiFi at the enterprise
level, you have to plan for failures in your storage layer.  Disks are
going to fail and you only get to choose how that failure will affect your
system.  Here are some things to think about.

+ Use RAID for data redundancy, to mitigate possible data loss when a disk
fails.  Buy spares.
+ Buy larger SSDs because they have greater reserve capacity and larger TBW
endurance.
+ Not all SSDs are created equal.  Some SSDs are cheaper with less
endurance on purpose.  "You get what you pay for."
+ Use SMART to monitor your SSDs.  They will tell you when their end of
life is near.

Hope this helps,
-- Mike


On Thu, Dec 13, 2018 at 4:05 AM Phil H  wrote:

> Hi there,
>
> I have been reading some reports of people having significant SSD
> degredation after 100+Tb of writes, due to the chemistry of NAND gates (or
> something?!).  Based on my current NiFi disk I/O, I think that works out 
to
> less than 12 months of usage.
>
> What are other users with large scale NiFi systems thinking/doing about
> this?
>
> Thanks,
> Phil
>

Re: [DISCUSS] Early, voluntary relocation to GitBox

[Arpad Boda]

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

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

[Arpad Boda]

+0



Guess these are not blockers, but found two issues:

  *   NiFi requires Java 8 or later, but doesn’t compile with Java 9. ( 
https://issues.apache.org/jira/browse/NIFI-5749 )
  *   Some tests fail on localized data ( 
https://issues.apache.org/jira/browse/NIFI-5750 )



Other than these verified:

-Signature

-Checksum

-Compiles (with Java 8  ) and starts without issues



Regards,

Arpad



On 24/10/2018, 23:18, "Marc Parisi"  wrote:



+1 ( binding )



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

)



Thanks,

Marc



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

wrote:



> +1 (binding)

>

> Ran through the release helper.

> No issue was found.

> Thanks for RM duties, Jeff!

>

> On Wed, Oct 24, 2018 at 1:42 PM James Wing  wrote:

> >

> > +1 (binding).  Ran though the release helper, tested the resulting

> binary.

> > Thank you for your persistence, Jeff.

> >

> >

> > On Mon, Oct 22, 2018 at 10:56 PM Jeff  wrote:

> >

> > > Hello,

> > >

> > > I am pleased to be calling this vote for the source release of Apache

> NiFi

> > > nifi-1.8.0.

> > >

> > > The source zip, including signatures, digests, etc. can be found at:

> > > https://repository.apache.org/content/repositories/orgapachenifi-1135

> > >

> > > The Git tag is nifi-1.8.0-RC3

> > > The Git commit ID is 98aabf2c50f857efc72fd6f2bfdd9965b97fa195

> > >

> > >

> 
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=98aabf2c50f857efc72fd6f2bfdd9965b97fa195

> > >

> > > Checksums of nifi-1.8.0-source-release.zip:

> > > SHA256:

> 6ec21c36ebb232f344493a4aeb5086eed0c462c576e11a79abed8149bc8b65c3

> > > SHA512:

> > >

> > >

> 
846aecd4eb497a3b7dee7d1911b02453b8162b6c87e39f3df837744a478212e2e3e3615921079d29c2804671f26ecd05b04ce46a4bb69e8911fc185e27be9c24

> > >

> > > Release artifacts are signed with the following key:

> > > https://people.apache.org/keys/committer/jstorck.asc

> > >

> > > KEYS file available here:

> > > https://dist.apache.org/repos/dist/release/nifi/KEYS

> > >

> > > 209 issues were closed/resolved for this release:

> > >

> > >

> 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=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: [EXT] XKCD use case for NiFi

[Arpad Boda]

Please create a Jira... __ 

On 03/10/2018, 21:08, "Peter Wicks (pwicks)"  wrote:

I don't think NiFi will run on his phone, MiNiFi maybe? 

-Original Message-
From: Joe Gresock [mailto:jgres...@gmail.com] 
Sent: Wednesday, October 3, 2018 12:08 PM
To: dev@nifi.apache.org
Subject: [EXT] XKCD use case for NiFi

https://xkcd.com/2054/

He needs NiFi!