Chris, thank you very much for suggesting a few alternatives. I'll tune my
flow this morning and give these a try, too. I think the path suggested by
Lars is going to prove ideal for my situation, where I want to enter my
ExecuteScript with one flowFile and create multiple flowFiles from that in
a
Hi all,
I am in the process of upgrading a NiFi cluster, but I am facing problems
and my ideas are starting to run out. I have gone through the mailing list
archive, but found nothing similar.
My working NiFi 1.13.2 cluster was already working in secure mode using
HTTPS, and also was configured w
Thanks for providing the configuration details and error message you are
receiving. The configuration properties listed appear correct, but the
error message seems to be related to class dependency issues.
Based on the exception message, it sounds like there may be an older
version of some NiFi l
Oh, forgot. Yeah
https://github.com/radiantone/pyfi-ui
This is just a functional NodeJS UI right now, the backend will come later.
From: Aaron Rich
Sent: Monday, July 19, 2021 10:43 AM
To: users@nifi.apache.org
Subject: Re: PYFI UI updates
Is this project poste
I am running NiFi 1.13.2 on Windows 2012 Server.
For any of my process blocks if I try to look at "Status History" I get a
dialog "Insufficient history, please try again later."
I *think* that these settings should provide me with *some* history but it very
well be that I am mistaken and have
Hi,
I am setting up NiFi cluster using kubernetes (Apache/NiFi image).
These are among paths to be persisted via persistent volumes:
* *nifi.flow.configuration.file (**flow.xml.gz)*
* *nifi.provenance.repository.directory.default***
* nifi.content.repository.directory.default
* nifi.flowfil
Hye All.
I was wondering what is the best way to access a sensitive context
parameter from ExecuteScript.
When adding a property on the ExecuteScript process, I can not put the
sensitive property.
Thanks for any input.
Regards
Etienne Jouvin
I would recommend keeping all of the above separate, so if you're running
multiple instances (pods/containers) on the same Node and mounting local
disk from the node into the instances as volumes, then have each instance
pointing at an instance-specific directory/file.
Each NiFi instance expects t
Hi,
You usually need to wait a few minutes after some data went through the
component to get something to display.
Are you experiencing this issue after a while even though data is going
through the component?
Please keep in mind that stats are removed after a restart when using the
volatile repos
Yes, data has been going through the components for at least two weeks on one
instance and a few hours on the other.
Same message on both systems for all components.
Thanks,
Matt
- Original Message - Subject: Re: Insufficient history, please
try again later
From: "Pierre Villa
Any error/message in nifi-app or nifi-user log files?
Le lun. 19 juil. 2021 à 18:32, a écrit :
> Yes, data has been going through the components for at least two weeks on
> one instance and a few hours on the other.
> Same message on both systems for all components.
>
> Thanks,
> Matt
>
>
>
Jim,
You can apply Chris's solution to ExecuteScript itself, as you can add
dynamic properties there and they will evaluate the EL for you. If you
set a dynamic property "myNode" to "${ip()}", you should be able to
use myNode.evaluateAttributeExpressions().getValue().
Regards,
Matt
On Mon, Jul 1
Hi,
according to NIFI-8246 defaults are
1.14.0:
nifi.sensitive.props.algorithm=NIFI_PBKDF2_AES_GCM_256
1.13.2
nifi.sensitive.props.algorithm=PBEWITHMD5AND256BITAES-CBC-OPENSSL
The same passwords don't work
My workaround was to export template from an old NiFi and to import it to a new
one
Trying to go from 1.13.2 to 1.14.0, but am getting this error:
2021-07-19 19:47:36,953 WARN [main]
org.apache.nifi.web.server.JettyServer Failed to start web server...
shutting down.
org.apache.nifi.encrypt.EncryptionException: Decryption Failed with
Algorithm [AES/GCM/NoPadding]
at
o
Hi Joe,
Thanks for providing the stack trace associated with the startup failure.
The problem is related to decryption of sensitive property values stored in
the flow.xml.gz configuration.
Can you provide the value of the following property from your
nifi.properties file?
nifi.sensitive.props.al
Hi Alexey,
Thanks for referencing the change in the default sensitive properties
algorithm. The encryption strategy is different between the two settings,
although the previous default value is still supported as an option.
For new installations of NiFi 1.14.0, NIFI_PBKDF2_AES_GCM_256 is preferr
16 matches
Mail list logo
