Hi
I don't know if these JIRAs are handling the same error I got with NIFI v.
1.15.3
https://issues.apache.org/jira/browse/NIFI-9546 PutTCP / PutUDP are
inefficient
https://issues.apache.org/jira/browse/NIFI-9571 PutTCP and PutUDP not
committing Session
But the PutCP process runs tasks continuous
Jens,
A quick look at the first Jira ticket you linked (NIFI-9564) mentions that
the processors have the "@TriggerWhenEmpty" annotation specified, which
means that they will continually trigger according to the configured
Scheduling even when there are no incoming FlowFiles. Whatsmore is that the
Hello,
>From what I understand from the documentation, the transit engine of
Hashicorp Vault is definitely supported for system properties. It is also
clear that the standard key/value engine of Hashicorp vault is supported
for sensitive processor properties (e.g. the password used to connect to a
Hi Cannon,
Both the HashiCorp Vault Transit and Key/Value Sensitive Property Providers
are able to protect NiFi's configuration files (e.g., nifi.properties,
login-identity-providers.xml, and authorizers.xml). In the case of the
Transit implementation, you would use the encrypt-config.sh tool fro
Hi Chris
Thanks for your reply. My work around is in fact, that I set the scheduling
to 1 sec. And hopefully it is fixed and well tested to the next release. I
just can't understand why a bug like this should come in a new release.
Kind regards
Jens M. Kofoed
Den tir. 1. feb. 2022 kl. 12.24 skre
Hi
I have a flow where I receive files which has been packed by tar and zip.
After unpacking the files I set the mime.type back to the original which
is: application/octet-stream
If I try to vied the content or download the content from a queue or
provance I get this error message: "Error parsing
