@ashutosh pathak The issue here is because of the Z literal on the date. You can handle it in the below expression ${start_date:replaceAll("Z$", "+0000"):toDate("yyyy-MM-dd'T'HH:mm:ss.SSSZ"):toNumber():plus(300000):toDate():format("yyyy-MM-dd'T'HH:mm:ss.SSSZ"):replace("+0000","Z")} Refer the Java Date Format specs here. EDIT A cleaner way, I just stepped on pattern letter X ${start_date:toDate("yyyy-MM-dd'T'HH:mm:ss.SSSX"):toNumber():plus(300000):toDate():format("yyyy-MM-dd'T'HH:mm:ss.SSSX")} ... View more

@ashutosh patha There is nothing programmatically in the way of importing templates from HDF 2.0 (NiFi 1.1.0+) to HDF 3.0 (NiFi 1.2.0+). There were however some issues identified in NiFi 1.x that affected the creation of good templates in some scenarios: https://issues.apache.org/jira/browse/NIFI-3173 (Fixed in HDF 2.1.1) https://issues.apache.org/jira/browse/NIFI-3509 (Fixed in HDF 2.1.4) If you first upgrade your HDF 2.1.4 and then create your templates you will be able to avoid any of those issues. You can also just manually copy your flow.xml.gz file from HDF 2.0 to HDF 3.0 nodes. Just keep in mind that all the sensitive properties in the flow.xml.gz file where encrypted using the sensitive properties key you provided during installation. In order to use the flow.xml.gz file from one NiFi installation in another NiFi installation you must use the same sensitive properties key. You could also use the sensitive properties migration toolkit to change the senstive props key and re-encrypt all teh values in a flow.xml.gz file before copying it to another NiFi install: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#sensitive-property-key-migration If you found this answer addressed your question, please click "accept" to close this thread. Thanks, Matt ... View more