gard...@solventum.com*
*A black background with green text Description automatically generated
*From:*Patrick Timmins
*Sent:* Wednesday, May 8, 2024 11:00
*To:* users@nifi.apache.org
*Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault
What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in
Ni
From:*Patrick Timmins
*Sent:* Wednesday, May 8, 2024 11:00
*To:* users@nifi.apache.org
*Subject:* [EXTERNAL] Re: IMDSv2 + Hashicorp Vault
What version of NiFi are you using? I'm seeing Spring v5. 3. 30 in
NiFi 1. 24. On 5/8/2024 6: 32 AM, Brant Gardner wrote: Good morning,
It appears that the Spring
What version of NiFi are you using? I'm seeing Spring v5.3.30 in NiFi 1.24.
On 5/8/2024 6:32 AM, Brant Gardner wrote:
Good morning,
It appears that the Spring 3.1.0 libraries that NiFi uses are unable
to work with IMDSv2 on AWS EC2 instances, so if your company requires
IMDSv2 (which ours
"The problem is that our PVCs aren't backed up, nor are they resilient
to an availability zone failure.
So I'm trying to find a method for backing up the flow files, but I've
not found anything for Kubernetes."
Yes, that's the problem; recommend configuring persistent storage for
the
Well there you go. This does not sound like a NiFi issue.
If you were using the default locations for the trust/keystore, those
may have changed going from RHEL7 to RHEL8. Change your configuration
to match the location of the trust/keystore on your RHEL8 system.
On 8/15/2023 8:43 AM,
Hello Richard,
Do you have *any* requests from the InvokeHTTP processor that are
actually getting through to the service running in the docker
container? Can you access the service that's running in the docker
container via another method (eg: browser or curl) to verify that you
have the
Hello Harshit ... I'm assuming "MyssqlTcp" is the name of a process
group in your NiFi GUI?? If so, can you show a screenshot of the NiFi
processors that are in that process group so we can see which processor
or where in the processing things might be hanging up?
Given no other info, the
distributed messaging layer (RabbitMQ,
Redis, AMQP, SQS). It will allow for runtime scripting of processors
using python and leverage a variety of transactional message brokers and
distributed topologies (e.g. AMQP).
Cheers!
Darren
On 2/21/2023 8:13 AM, Patrick Timmins wrote:
So this looks
So this looks a lot like the "PyFi" related projects that you put out on
GitHub back in ~ July 2021. But the GitHub stuff that I'm seeing for
ElasticCode are just all stub projects ... and they look like they were
created just a few weeks ago:
https://github.com/elasticcode-ai/elasticcode
There's an easy way to find out for yourself. Your investigation into
the product should be thorough enought to provide you the experience you
need to make that call for your customer (... no second hand info
required!).
On 2/16/2023 11:00 AM, Snyder, David B. wrote:
Hello –
Does anyone
Also, deprecated doesn't mean not functioning/supported, so you might
just go ahead and upgrade NiFi while leaving your current
dataflow/processors "as is" ... and then start incrementally replacing
the deprecated processors with whatever is available in the version of
NiFi to which you
In addition to the other suggestions, the last time I checked, the HTML5
of the NiFi interface won't render if you're using Edge or IE to
access. Brave, Chrome, Firefox etc will work, however.
On 11/8/2022 1:53 PM, James McMahon wrote:
Has anyone successfully configured NiFi on AWS, and
nifi.content.repository.archive.max.usage.percentage=50%
nifi.content.repository.archive.enabled=true
nifi.content.repository.always.sync=false
nifi.content.viewer.url=../nifi-content-viewer/
So we even use 10MB…
will check if lowering the value changes anything
On 22-09-13 20:04, Patrick Timmins wrote:
No, I
No, I agree. Lars, please give up the rest of your evening and drive
back to work and report back with your findings ASAP. It may be past
normal working hours in Germany, but you have NiFi brothers and sisters
around the world that are counting on you ... please don't let us down.
:) <-
You can always write your own processor using the NiFi processor API:
https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#processor_api
... or you can write your own code in several different languages
(Groovy, Python, Ruby, etc) and run it using the NiFi ExecuteScript
processor:
so that is does the risky "not recommended" things
mentioned above. But that doesn't mean that "no trust store is needed
or involved".
There are some good tutorials out there for using keytool and openssl
for setting up PKI for client/server 2-way authentication.
Pat
channel.
But none of this has anything to do with NiFi ... this is all just
normal PKI / TLS / openssl / keytool stuff.
Pat
--
Patrick Timmins
https://www.linkedin.com/in/patrick-timmins/
On 5/12/2022 10:47 AM, Bryan Bende wrote:
Hello,
You have to use the toolkit again to create more
:
Nope, already checked that.
On Fri, Apr 10, 2020 at 8:23 PM Patrick Timmins <mailto:ptimm...@cox.net>> wrote:
No issues here. Sounds like a timezone / system clock / clock
drift issue (in a cluster).
On 4/10/2020 11:59 AM, Joe Witt wrote:
The provenance repo is in la
No issues here. Sounds like a timezone / system clock / clock drift
issue (in a cluster).
On 4/10/2020 11:59 AM, Joe Witt wrote:
The provenance repo is in large scale use by many many users so
fundamentally it does work. There are conditions that apparently need
improving. In the past
19 matches
Mail list logo
