@Vivek Singh Try the following configuration in your splitJson processor: Thanks, Matt If you found this answer addressed your initial question, please take a moment to login and click "accept". ... View more

@Tanmoy NiFi templates where never intended when they were designed for the purpose of version control. A template by design bundles everything that the selected components need to work. Also to make sure templaet could be deployed to any other environment, all sensitive properties are cleared. The NIFi team realized that design made it less then ideal for dataflow promotion between environments. That is where the NiFi Registry came int to the picture (Available as of Apache NiFi 1.5 and HDF 3.1.x) https://nifi.apache.org/registry.html The NIFi Registry runs as an external service but complimentary service to NiFi. Multiple NiFi instances/clusters can be configured to access the same registry. User can start version control on process groups within NiFi which stores a version controlled copy of the flow (similar to a template) in the NIFi Registry. User on another NiFi instance/cluster can connect to the same registry and load that flow on to their NiFi. Initially adding a flow form the registry works just like templates (Need to enter sensitive properties and controller services are copied over.) What is different is how that info is preserved through version upgrades from that point forward. Let say on system one (dev) and new version of that version controlled process group is pushed to the registry. On System two they can upgrade to version 2 without needing to reset sensitive properties or worry about getting another copy of a controller service. Thank you, Matt *** If you found this answer addressed your initial question, please take a moment to login and click on "Accept". ... View more

@Patrick There may issues external to a processors code execution that can result in a stoppage in a dataflow. The Monitor activity processor can be placed inline anywhere in your flow to monitor FlowFiles passing through it on a configurable interval. The processor then will generate alert type FlowFiles when a activity is outside of those thresholds. You could then send those generated alert messaged to a putEmail processor to send out a notification of an outage. Not all failures are unexpected, Often times a second attempt is successful. Setting up a count loop is a good way of having FlowFiles that are routed to failure to to try x number of times in a loop before taking some other action. https://cwiki.apache.org/confluence/download/attachments/57904847/Retry_Count_Loop.xml?version=1&modificationDate=1433271239000&api=v2 You may also want to consider looking at the SiteToSiteBulletinReportingTask. NiFi processor produce bulletins for ERROR and WARN level logs. With this reporting task, you can feed these produced bulletins back to same NiFi or another NiFi where they can be handled like any other FlowFile and pushed to what ever database you want. Thank you, Matt *** If you found this answer addressed your question, please take a moment to login and click "accept" ... View more

@Sonny Chee What version of HDF are you running? Is it HDF 3.1? Is your NiFi secured and using Ranger for NiFi authorizations? If so, you may have run into this identified bug: https://issues.apache.org/jira/browse/NIFI-4925 There are currently no HDF releases with the fix included. Thank you, Matt ... View more