{ "operation": "default", "spec":{ "*" : { "flow_file_id" : "${uuid}" } } } this spec is generating the same uuid for all the objects in the array of json.  ... View more

Hi @ydavis ,   I found out the https://hub.helm.sh/charts/cetic/nifi which is only supported single node NiFi on Kubernetes now, is right? Is the multi-node NiFi cluster on Kubernetes still developing? ... View more

Glad that worked! Concerning group permission definitely a known issue, don't believe there's a public work ticket that you can follow. ... View more

Resource for processor is not /processor but is instead /processors. Policies for reading and writing processors is /processors/{uuid} and /data/processors/{uuid} ... View more

Excellent post, very well explained and extremely helpful. ... View more

I have tried this mechanism and it works really well when using parameters for processors. But when it comes to parametrising controller services, the new key value pairs or updated key value pairs reflect in the services only after we restart the NiFi service. Is there a workaround to this?? The reason to parameterise controller service is that in an enterprise say we have many Oracle databases. Should we be creating a new controller service for every database or have just one controller service and pass it values from an external properties file?? ... View more

@Sami Ahmad Instead of left clicking on the link in step three, right click and select "Save Link As..." option to save the xml template so it can be imported in to your NiFi. The dataflow template will show you all the components needed for this workflow. I believe the intent of this tutorial was not to teach users how to use the NiFi UI, but rather how to use a combination of specific NiFi components to build accomplish a particular workflow. Using the NIFi UI dataflow tools you can recreate the workflow as a UI dataflow building exercise. Thanks, Matt ... View more

Hi Yolada, How do you pass flowfile attributes into your JOLT Transformation? Thanks, ... View more