Re: HiveConnectionPool is not known

2022-12-01 Thread Joe Witt
Shawn

I have your email on bcc so you see this but you'll need to subscribe to
the list to see these otherwise and for your messages to get through
without moderation.

The Hive nars are removed from our convenience binary due to their size and
dependency complexity but as noted in our migration guidance [1] under the
'1.17.0' section - you can still get them from Maven central [2].

[1] https://cwiki.apache.org/confluence/display/nifi/migration+guidance
[2]
https://mvnrepository.com/artifact/org.apache.nifi/nifi-hive-services-api-nar
 https://mvnrepository.com/artifact/org.apache.nifi/nifi-hive-nar

Thanks

On Thu, Dec 1, 2022 at 3:42 PM  wrote:

> When trying to drop a template on the flow I get this error:
>
> org.apache.nifi.dbcp.hive.HiveConnectionPool is not known to this NiFi
> instance.
>
> This template was from an older nifi instance.
>
>
>
> Where can I find the nar or driver for this?
>
> Or maybe there is a way around this? like editing the template or
> something.
>
>
>
>
>
>
>
>
>
>
>
> Shawn Craig
>
> VP, Senior Information Security Engineer  |  ICSCYBER
>
> [image: signature_3995171575]
>


HiveConnectionPool is not known

2022-12-01 Thread Shawn.Craig
When trying to drop a template on the flow I get this error:
org.apache.nifi.dbcp.hive.HiveConnectionPool is not known to this NiFi instance.
This template was from an older nifi instance.

Where can I find the nar or driver for this?
Or maybe there is a way around this? like editing the template or something.





Shawn Craig
VP, Senior Information Security Engineer  |  ICSCYBER
[signature_3995171575]


[VOTE] Release Apache NiFi 1.19.1 (RC1)

2022-12-01 Thread Joe Witt
Hello,

I am pleased to be calling this vote for the source release of Apache
NiFi 1.19.1.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1217

The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.19.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.19.1-RC1
The Git commit ID is 16ba0c2a5a61e98c5a73769976d8589932bfd43d
https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=16ba0c2a5a61e98c5a73769976d8589932bfd43d

Checksums of nifi-1.19.1-source-release.zip:
SHA256: 0d88e02a00b3fca4ee4c453788caf3ea1cc8d8f3be7ee2e2bd395ce25932bd7e
SHA512: 
861121c17a67020d34f3457d047c3c0486e3c6bd6392bf355f8bdf6f3eed01e7ea441f1175e8232c354a9ebf0c2f709ddf846e694bc2480305d180b0a692ec49

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

26 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12352626

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.19.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.19.1
[ ] +0 no opinion
[ ] -1 Do not release this package because...


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

2022-12-01 Thread Marc Parisi
+1 binding.

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

Great work team!

Thanks,
Marc

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

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


Re: [discuss] nifi 1.19.1

2022-12-01 Thread Joe Witt
RC1 for 1.19.1 build is underway.  Should ideally have the bits/vote
up within the next 2-3 hours.

Thanks

On Thu, Dec 1, 2022 at 9:51 AM Joe Witt  wrote:
>
> Yep I got it.  Thanks
>
> On Thu, Dec 1, 2022 at 9:33 AM David Handermann
>  wrote:
> >
> > Joe,
> >
> > One additional note for 1.19.1, the following Jira issue and associated
> > pull request just merged resolve a regression in Kafka component
> > configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
> > Mechanism:
> >
> > https://issues.apache.org/jira/browse/NIFI-10919
> >
> > Regards,
> > David Handermann
> >
> > On Wed, Nov 30, 2022 at 1:55 PM Joe Witt  wrote:
> >
> > > Grabbed all the goods from main post 1.19 and have them on branch
> > > 'support/nifi-1.19'
> > >
> > > Waiting on https://issues.apache.org/jira/browse/NIFI-10914 and then
> > > will roll with the 1.19.1 RC.
> > >
> > > Thanks
> > >
> > > On Wed, Nov 30, 2022 at 8:23 AM Joe Witt  wrote:
> > > >
> > > > Team,
> > > >
> > > > I'm thinking it might be worthwhile to spin up a 1.19.1.  Want to be
> > > > respectful of everyone's time as I realize these votes aren't always
> > > > easy to participate in.
> > > >
> > > > The main reason has to do with the registry/client changes and how
> > > > that has been creating problems for people as they upgrade past 1.16.
> > > > We thought it was sorted in 1.19 but not so - as shown in
> > > > https://issues.apache.org/jira/browse/NIFI-10874.  For those watching
> > > > in Slack this has been biting several users lately.
> > > >
> > > > I'll sweep up existing already landed items that are easily ported over.
> > > >
> > > > I do realize we've got the nar plugin being updated to help detect
> > > > dupe dependencies in nar chains as well as to help with reproducible
> > > > builds but we could pull that in for 1.19.2 if we have one but
> > > > certainly 1.20.
> > > >
> > > > Thanks
> > >


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

2022-12-01 Thread Jeremy Dyer
+1 (binding)

verified source, build from source on U22.04, verified functioning docker
builds, and confirmed valid SHAs

On Thu, Dec 1, 2022 at 10:16 AM Gábor Gyimesi  wrote:

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


Re: [discuss] nifi 1.19.1

2022-12-01 Thread Joe Witt
Yep I got it.  Thanks

On Thu, Dec 1, 2022 at 9:33 AM David Handermann
 wrote:
>
> Joe,
>
> One additional note for 1.19.1, the following Jira issue and associated
> pull request just merged resolve a regression in Kafka component
> configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
> Mechanism:
>
> https://issues.apache.org/jira/browse/NIFI-10919
>
> Regards,
> David Handermann
>
> On Wed, Nov 30, 2022 at 1:55 PM Joe Witt  wrote:
>
> > Grabbed all the goods from main post 1.19 and have them on branch
> > 'support/nifi-1.19'
> >
> > Waiting on https://issues.apache.org/jira/browse/NIFI-10914 and then
> > will roll with the 1.19.1 RC.
> >
> > Thanks
> >
> > On Wed, Nov 30, 2022 at 8:23 AM Joe Witt  wrote:
> > >
> > > Team,
> > >
> > > I'm thinking it might be worthwhile to spin up a 1.19.1.  Want to be
> > > respectful of everyone's time as I realize these votes aren't always
> > > easy to participate in.
> > >
> > > The main reason has to do with the registry/client changes and how
> > > that has been creating problems for people as they upgrade past 1.16.
> > > We thought it was sorted in 1.19 but not so - as shown in
> > > https://issues.apache.org/jira/browse/NIFI-10874.  For those watching
> > > in Slack this has been biting several users lately.
> > >
> > > I'll sweep up existing already landed items that are easily ported over.
> > >
> > > I do realize we've got the nar plugin being updated to help detect
> > > dupe dependencies in nar chains as well as to help with reproducible
> > > builds but we could pull that in for 1.19.2 if we have one but
> > > certainly 1.20.
> > >
> > > Thanks
> >


Re: [discuss] nifi 1.19.1

2022-12-01 Thread David Handermann
Joe,

One additional note for 1.19.1, the following Jira issue and associated
pull request just merged resolve a regression in Kafka component
configuration when using SCRAM-SHA-256 or SCRAM-SHA-512 as the SASL
Mechanism:

https://issues.apache.org/jira/browse/NIFI-10919

Regards,
David Handermann

On Wed, Nov 30, 2022 at 1:55 PM Joe Witt  wrote:

> Grabbed all the goods from main post 1.19 and have them on branch
> 'support/nifi-1.19'
>
> Waiting on https://issues.apache.org/jira/browse/NIFI-10914 and then
> will roll with the 1.19.1 RC.
>
> Thanks
>
> On Wed, Nov 30, 2022 at 8:23 AM Joe Witt  wrote:
> >
> > Team,
> >
> > I'm thinking it might be worthwhile to spin up a 1.19.1.  Want to be
> > respectful of everyone's time as I realize these votes aren't always
> > easy to participate in.
> >
> > The main reason has to do with the registry/client changes and how
> > that has been creating problems for people as they upgrade past 1.16.
> > We thought it was sorted in 1.19 but not so - as shown in
> > https://issues.apache.org/jira/browse/NIFI-10874.  For those watching
> > in Slack this has been biting several users lately.
> >
> > I'll sweep up existing already landed items that are easily ported over.
> >
> > I do realize we've got the nar plugin being updated to help detect
> > dupe dependencies in nar chains as well as to help with reproducible
> > builds but we could pull that in for 1.19.2 if we have one but
> > certainly 1.20.
> >
> > Thanks
>


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

2022-12-01 Thread Gábor Gyimesi
+1 (non-binding)

- verified signature and hashes of source tar.gz file
- verified git commit hash
- built RC core and all extensions (excluding Tensorflow) with GCC 11.3 on
Ubuntu 22.04
- ran all unit, integration and docker system tests
- verified contents of README.md, NOTICE, and LICENSE files
- verified
https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/nifi-minifi-cpp-0.13.0-bin-linux.tar.gz
binary with simple flows having TailFile, GetFile, LogAttribute processors
and communication through InvokeHTTP processor with NiFi's ListenHTTP
processor
- verified Prometheus metrics reporting with built binary and Prometheus
2.35.0

Thanks,
Gabor

On Wed, 30 Nov 2022 at 11:58, Ferenc Gerlits  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> MiNiFi C++ 0.13.0.
>
> The source tarball, the binary build, plus signatures and digests can be
> found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.13.0/
>
> The Git tag is minifi-cpp-0.13.0-RC1
> The Git commit ID is 4389b9ac05e43e1dbf908e9014787d07c8a9cd05
>
> https://github.com/apache/nifi-minifi-cpp/commit/4389b9ac05e43e1dbf908e9014787d07c8a9cd05
>
> Checksums of nifi-minifi-cpp-0.13.0-source.tar.gz:
> SHA256: 9cbc37cb841dbd2b53412ded7ba59cd571181b659f647b9d35c3f3ac985337c1
> SHA512:
>
> 3a69ef1894e4fdc2b2e4d7cd77f46debd86c52a70cfd1a7a76445ae976cfe12bd176cfad3a6aacda2a01aa2ff5810faf2e3d3a8e8ff0de5e460ae19f63db
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/fgerlits.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 85 issues were closed/resolved for this release:
> https://issues.apache.org/jira/projects/MINIFICPP/versions/12351771
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65145325#ReleaseNotesMiNiFi(C++)-Versioncpp-0.13.0
>
> The vote will be open for 72 hours.
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test. Then
> please vote:
>
> [ ] +1 Release this package as nifi-minifi-cpp-0.13.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>


Re: understand nifi usage patterns

2022-12-01 Thread ski n
"The use cases for which Nifi is used/adopted does the data load belongs to
streaming mode or pure batch workloads"

Actually for both. NiFi is used for creating data flows.

Data flows can be used for:

- Data ingesting (gathering data from a lot of sources)
- Data offloading (load data to other platforms like Apache Kafka, Hadoop,
Azure Data Explorer etc)
- Data integration (Connecting applications)
- Edge data (gathering data from IOT sensors) / in combination with MiNiFi)

Besides such use cases Apache NiFi does a good job in visualize and manage
these data flows and scale them when needed.

More reading: https://nifi.apache.org/docs/nifi-docs/html/overview.html

Raymond






On Thu, Dec 1, 2022 at 12:19 PM Tanmaya Panda
 wrote:

> Hi Team,
>
> We are working on developing a Nifi connector to send and receive data
> from Azure Data Explorer( a fast and fully managed data analytics service
> offering for relatime analysis on large volumes of data streaming from IOT
> devices, applications etc.).
>
> We wanted to understand the general usage patterns of Nifi. The use cases
> for which Nifi is used/adopted does the data load belongs to streaming mode
> or pure batch workloads?
>
> Thanks,
> Tanmaya
>


understand nifi usage patterns

2022-12-01 Thread Tanmaya Panda
Hi Team,

We are working on developing a Nifi connector to send and receive data from 
Azure Data Explorer( a fast and fully managed data analytics service offering 
for relatime analysis on large volumes of data streaming from IOT devices, 
applications etc.).

We wanted to understand the general usage patterns of Nifi. The use cases for 
which Nifi is used/adopted does the data load belongs to streaming mode or pure 
batch workloads?

Thanks,
Tanmaya