Info required for service upgrade

[Ganesh, B (Nokia - IN/Bangalore)]

Hi ,

We have requirement to upgrade version of Nifi-cluster without incurring 
service downtime or without affecting data-loss.
For that, is it necessary to suspend the current template running in Nifi 
before start of the version upgrade activity? If yes, whether there is any 
programmatic way (i.e. through REST call or some other java API based 
mechanism) to suspend and resume the complete template running in Nifi?
If your answer is no to the former question, can you please point us to the 
relevant design documentation in Nifi internal which enables this nice 
functionality i.e. version upgrade possibility without service downtime and 
data loss in Nifi-cluster.

Thanks & Regards,
Ganesh.B

PutTCP delays when multithreaded

[Phil H]

If I have more than one thread running for a PutTCP processor, it seems to
add nearly 1 second of latency, even when I am only sending a single flow
file through my system.

This multiplexing does increase the total throughout of my system (items
per hour) but this latency is hard to explain.

Any ideas?

Re: [VOTE] Release Apache NiFi 1.12.0

[Andy LoPresto]

+1 (binding). 

Verified the release info (signature, digests [equal to provided digests; 
different from email as noted in other thread], etc.), the full build, and some 
flows exercising new cryptographic metadata. Great work on this enormous 
release everyone. 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Aug 13, 2020, at 1:31 PM, Joe Witt  wrote:
> 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.12.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1165
> 
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.0/
> 
> A helpful reminder on how the release candidate verification process works:
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> 
> The Git tag is nifi-1.12.0-RC1
> The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> 
> Checksums of nifi-1.12.0-source-release.zip:
> SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> SHA512:
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 335 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346778
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.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.12.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...

Re: Checksums don't match in 1.12 release vote

[Joe Witt]

will correct those - the git commit id, checksums, etc.. are all from
previous release.  fixing

On Thu, Aug 13, 2020 at 2:22 PM Mike Thomsen  wrote:

> In the repo (and what I can reproduce locally) for 256:
>
> 0abf5d5273e00b62790f143cdf878128b637e57e9fcf9e7978555d386eba5fff
>
> vs
>
> a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
>
> in the vote thread.
>

Re: Live development of custom processors and JAVA_HOME--confirm best practice

[Mike Thomsen]

> all day long like IntelliJ IDEA (and others) march on requiring later and 
> later Java versions.

All of my teammates and I are using AdoptOpenJDK 8 with IntelliJ and
in production. Not sure what issue you're running into, but we're on
8u262 as far as I know.

On Thu, Aug 13, 2020 at 1:49 PM Russell Bateman  wrote:
>
> When installing NiFi in production, Ansible can be used to set up
> JAVA_HOME. There is zero problem for users of NiFi.
>
> However, from a development host, given the now rapid cadence of Java
> releases, we sometimes run into problems launching a private
> installation of NiFi in the course of testing or debugging our custom
> processors because tools used minute-to-minute and all day long like
> IntelliJ IDEA (and others) march on requiring later and later Java versions.
>
> I found an old JIRA issue that suggests a solution for NiFi 0.1.0, that
> of working around the problem by setting java=  in /conf/bootstrap.conf/
> to point to a valid Java 1.8 JRE/JDK. This sounds good to me, but the
> version is very old.
>
> Is this still best practice?
>

Checksums don't match in 1.12 release vote

[Mike Thomsen]

In the repo (and what I can reproduce locally) for 256:

0abf5d5273e00b62790f143cdf878128b637e57e9fcf9e7978555d386eba5fff

vs

a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63

in the vote thread.

[VOTE] Release Apache NiFi 1.12.0

[Joe Witt]

Hello,

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

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

The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.0/

A helpful reminder on how the release candidate verification process works:
https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate

The Git tag is nifi-1.12.0-RC1
The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae

Checksums of nifi-1.12.0-source-release.zip:
SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
SHA512:
2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953

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

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

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

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

Re: Nifi Authentication

[Andy LoPresto]

There is no support for Basic Authentication to access the NiFi UI / API. 

Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Aug 13, 2020, at 11:57 AM, Ashar Azmat  wrote:
> 
> Hello team,
> 
> Hope this email finds you well. We had a question in regards to 
> authentication in relation to the Nifi User Interface.
> We would like to enable authentication by using basic authentication. Is 
> there any native basic authentication support or do we have to use an 
> alternative authentication mechanism such as Kerberos or LDAP?
> 
> We would appreciate your help in this regard.
> 
> Best,
> Ashar
> ::DISCLAIMER::
> 
> The contents of this e-mail and any attachment(s) are confidential and 
> intended for the named recipient(s) only. E-mail transmission is not 
> guaranteed to be secure or error-free as information could be intercepted, 
> corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses 
> in transmission. The e mail and its contents (with or without referred 
> errors) shall therefore not attach any liability on the originator or HCL or 
> its affiliates. Views or opinions, if any, presented in this email are solely 
> those of the author and may not necessarily reflect the views or opinions of 
> HCL or its affiliates. Any form of reproduction, dissemination, copying, 
> disclosure, modification, distribution and / or publication of this message 
> without the prior written consent of authorized representative of HCL is 
> strictly prohibited. If you have received this email in error please delete 
> it and notify the sender immediately. Before opening any email and/or 
> attachments, please check them for viruses and other defects.
> 

Nifi Authentication

[Ashar Azmat]

Hello team,

Hope this email finds you well. We had a question in regards to authentication 
in relation to the Nifi User Interface.
We would like to enable authentication by using basic authentication. Is there 
any native basic authentication support or do we have to use an alternative 
authentication mechanism such as Kerberos or LDAP?

We would appreciate your help in this regard.

Best,
Ashar
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: Live development of custom processors and JAVA_HOME--confirm best practice

[Andy LoPresto]

Russell, 

To develop and test against multiple versions of Java, I (and I’m aware other 
committers) use jenv [1] which is a version manager for Java. You can set a 
specific version for global/shell/local environments, and it allows switching 
very quickly. 

I generally run these two commands to switch:

$ jenv shell 1.8.0 # switch to JDK 8
$ jjh # alias defined below

# In my .zshrc (or whatever shell configuration file you use)
alias jjh='jenv version && jenv macos-javahome && jenv_set_java_home && jenv 
doctor’
alias jenv_set_java_home='export JAVA_HOME="$HOME/.jenv/versions/`jenv 
version-name`" && echo "JAVA_HOME=$JAVA_HOME”'

Setting the $JAVA_HOME ensures that mvn picks up the right Java version when it 
runs. 

[1] https://www.jenv.be/ 



Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Aug 13, 2020, at 10:48 AM, Russell Bateman  wrote:
> 
> When installing NiFi in production, Ansible can be used to set up JAVA_HOME. 
> There is zero problem for users of NiFi.
> 
> However, from a development host, given the now rapid cadence of Java 
> releases, we sometimes run into problems launching a private installation of 
> NiFi in the course of testing or debugging our custom processors because 
> tools used minute-to-minute and all day long like IntelliJ IDEA (and others) 
> march on requiring later and later Java versions.
> 
> I found an old JIRA issue that suggests a solution for NiFi 0.1.0, that of 
> working around the problem by setting java=  in /conf/bootstrap.conf/ to 
> point to a valid Java 1.8 JRE/JDK. This sounds good to me, but the version is 
> very old.
> 
> Is this still best practice?
> 

Live development of custom processors and JAVA_HOME--confirm best practice

[Russell Bateman]

When installing NiFi in production, Ansible can be used to set up 
JAVA_HOME. There is zero problem for users of NiFi.


However, from a development host, given the now rapid cadence of Java 
releases, we sometimes run into problems launching a private 
installation of NiFi in the course of testing or debugging our custom 
processors because tools used minute-to-minute and all day long like 
IntelliJ IDEA (and others) march on requiring later and later Java versions.


I found an old JIRA issue that suggests a solution for NiFi 0.1.0, that 
of working around the problem by setting java=  in /conf/bootstrap.conf/ 
to point to a valid Java 1.8 JRE/JDK. This sounds good to me, but the 
version is very old.


Is this still best practice?

MongoDB Connection Issue

[Venkatesh Raman]

Hi,

I've set NiFi on my local machine for my learning purposes. I'm trying to
do a small poc pipeline which loads the data from my local system to
MongoDB, which is hosted on cloud.

But, when giving the mongodb connection string as, 'mongodb+srv://', it
didn't work. I tried removing the srv and gave it as 'mongodb://', I'm
getting a connection timed out error "Timed out after 3 ms while
waiting for a server"

Is it a mongo db driver related? I'm using NiFi version 1.11.4. I want to
know the version of mongo db driver and how we can to mitigate this issue.

Thanks,
Venkatesh Raman