@thuylevn    The ConvertJsonToAvro processor was removed from the default NiFi distribution bundle because of space limitations as of the Apache NiFi 1.10 release.   https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance The ConvertJSONToAvro processor was part of the nifi-kite-nar https://github.com/apache/nifi/tree/master/nifi-nar-bundles/nifi-kite-bundle   Hope this helps, Matt ... View more

@vikrant_kumar24    The ExecuteStreamCommand processor is not doing anything fancy here.  It is just trying to execute the command you enter.  Assuming the command was "myscript.py", The executeStreamCommand would be doing same thing as you would if you opened a terminal window on your NiFi node and clicked on "myscript.py" to run it.  Keep in mind that NiFi is performing this action as the user that owns the NiFi java process.  The ExecuteStreamCommand processor will pass the FlowFiles content (if there is any) to stdin.   Have you perhaps looked at the ExecuteScript processor instead?   Hope this helps, Matt ... View more

@DavidR  NiFi requires that a sensitive properties key has been configured.  The Sensitive properties key is used to encrypt all passwords written to the flow.xml.gz file.   The flow.xml.gz is not portable between different installations of NiFi unless at least 1 of the 2 following is true: 1. Both NiFi installations are using the exact same sensitive properties key in the nif.properties file: nifi.sensitive.props.key= All the sensitive properties (passwords) entered in to components configured in your dataflows contained within the flow.xml.gz are encrypted.  NiFi will fail to start if it cannot decrypt these sensitive properties as the flow.xml.gz is uncompressed and loaded in to memory. 2. The  flow.xml.gz contains no encrypted sensitive properties.  If you do not know the sensitive properties key used on NiFi where the flow.xml.gz was obtained, you can uncompress the flow.xml.gz yourself and remove all occurrences of "enc{.*}".  For example: <value>enc{2fecf4bbb0456fd10c088f73aab2b3c3e92b532afa46eb042f0b0a14b06b1b60}</value> would be replaced with: <value></value> Then gzip the flow.xml again. This removes all passwords from your flow.xml.gz will allowing it to be loaded by any new NiFi installation.  You will then need to go through your components and set the passwords again which will then get encrypted to the flow.xml.gz using the sensitive props key set on that NiFi.   Hope this helps, Matt ... View more

@Umakanth    NiFi components (Processors, controller services, reporting tasks, etc.) that have password properties do not support retrieving these passwords from an external source or service.  NiFi not only obscures the passwords in the UI, but also encrypts all those passwords when they are written to disk in the flow.xml.gz.  Additionally, for passwords entered in the various NiFi configuration files, NiFi offers and encrypt config toolkit that can encrypt all these sensitive properties in these configuration files on disk.   I suggest maybe opening an Apache NiFi Jira with details around what you are trying to accomplish here for a possible future feature. - For passwords utilized through NiFi dataflow components, my thought here would be maybe around a NiFi controller service for connecting to such external services.  This would also require that processors that would need to use this new NiFi Controller Service to retrieve passwords would all need to be modified as well with new configuration properties to interface with the new controller service.   This is by no means a simple change in NiFi, but getting the idea out there with some strong use case for it can get the ball rolling in the community.   Hope this helps, Matt ... View more