We are upgrading from 2.0.0 M4 to 2.4.0 in EKS via helm charts. But encountering issue while running nifi.sh file. Nifi.sh file references nifi-env.sh which is empty. We are suspecting issue is with docker image of nifi. When we opened binary of nifi 2.4.0 which is downloaded locally from internet, I can see content inside nifi-env.sh.  Same is not present inside EKS when we deploy nifi 2.4.0 docker image into EKS This is crashing our main container. Basically its not setting PID path. ... View more

When we are trying to upgrade apache nifi from 2.0.0 m4 to 2.4.0, We are getting this error  "/opt/nifi/nifi-current/bin/nifi.sh: 276: exec: 04:10:55,565: not found" The nifi.sh file is taking some time stamp/junk value in its on of the exec command. this is snippet from nifi.sh which is causing issue. if [ "$1" = "run" ]; then RUN_COMMAND=$(eval "${run_bootstrap_cmd} get-run-command") RUN_COMMAND_STATUS=$? if [ $RUN_COMMAND_STATUS = 0 ]; then exec $RUN_COMMAND else echo "Failed to get run command" echo "${RUN_COMMAND}" exit 1 fi We are upgrading nifi in EKS, we can not edit or touch files from official docker image. Can some one help to fix this issue? ... View more

We are using nifi as api gateway. Whenever we pass any attributes in request header it should be captured as http.headers.xxxx in flowfile but when checked in flowfile ; header value is coming in small case though we have passed it in caps. In our implementation we have 2 instances of nifi running. One instance doesn't have any issue where as other has . Please help if there is any configuration I'm missing.  ... View more