Shawn,
We've done this ad hoc in other places when it made sense to do so.
Maybe we'd want to avoid adding any record values to the error
message, although since the attribute is associated with the flow file
content I'm not sure that's necessary from a security perspective. The
only other thing
I’d like to get some feedback on an enhancement that I’m looking at doing. I
need a way for a custom Record Reader to pass information downstream on parse
failures so that they can be logged for futhur investigation by a human. I’d
like to have AbstractRecordProcessor add an attribute
I recognize that running NiFi on Kubernetes isn't quite as easy as starting it
in Docker but it's also not that hard if you've worked with Kubernetes a bit.
More than likely the issue is in your Kubernetes Yaml that you used to deploy
NiFi with. This is separate than nifi.properties and would
Public
Hi Endre,
I certainly agree with the bare metal option. The reason I have a specific
request for OpenShift is the requirement to adhere to organisational
architectural road map.
I cannot agree more that it is not a single person task. I was working on it
for few days with OpenShift
Public
Hi Shawn,
Thank you for your reply. Yes, I did have persistent volume, as per attached
scripts.
I removed all volume configs now because it caused another error:
/opt/nifi/nifi-current/conf/nifi.properties: No such file or directory I didn't
think I need to supply nifi.properties file
Hi,
If to make NiFi work on K8S is a beast, then to make it work on Openshift, is a
category-5 Kaiju [1][2].
This is definitely not a few days task for a single person.
Why not run NiFi just in docker (docker-compose)? Or on bare metal?
Best regards,
Endre
[1]
That error is caused by incorrect permissions on the volume but I'm not sure
why. Can you share your Kubernetes Yaml file, it will make it easier to track
down the difference? Also what are you using for a persistence volume?
Thanks
Shawn
On 2/12/20, 1:14 PM, "Fill, Natalia" wrote:
Public
Hi,
I am trying to run Nifi pod on OpenShift for several days now and unfortunately
unsuccessfully.
The error that I am getting persistently is
replacing target file /opt/nifi/nifi-current/conf/nifi.properties
sed: couldn't open temporary file /opt/nifi/nifi-current/conf/sedXGg2lo:
