I have an update on this question which remained quite rightly
unanswered since it was my own peculiar problem.
It resulted from the not-so-clever way our NiFi systemdservice was put
together 6+ years ago which was avoided using /nifi.sh/ (and
/nifi-env.sh/).NIFI_HOMEsimply did not exist once NiFi was launched.
In the much more recent Docker container instance as well as from the
development host command line directly (/nifi.sh/), NIFI_HOMEis present.
On 6/7/24 15:46, Russell Bateman wrote:
It's hard for me to determine this for customers who may already have
installed Apache NiFi and just drop my NAR in or count on my Docker
container. I'd like a clearer idea of who or what is responsible for that.
