@Anishkumar Valsalam In a Nifi cluster you need to make sure you have uploaded you new custom component nars to every node in the cluster. I do not recommend adding your custom nars directly to the existing NiFi lib directory. While this works, it can become annoying to manage when you upgrade NiFi versions. NiFi allows you to specify an additional lib directory where you can place your custom nars. Then if you upgrade, the new version can just get pointed at this existing additional lib dir. Adding additional lib directories to your NiFi is as simple adding an additional property to the nifi.properties file. for example: nifi.nar.library.directory.lib1=/nars-custom/lib1 nifi.nar.library.directory.lib2=/nars-custom/lib2 Note: Each prefix must be unique (i.e. - lib1 and lib2 in the above examples). These lib directories must be accessible by the user running your NiFi instance. Thanks, Matt ... View more

@spdvnz There currently is no HDF release that is based off Apache NiFi 1.1.2. The most current HDF release as of this response if HDF 2.1.2. The HDF 2.1.x versions are all based off Apache NiFi 1.10 plus additional Apache bug fixes. The additional bug fixes included in each of these bug fixes can be found in the release notes for each HDF release. HDF 2.1.0 release notes HDF 2.1.1 release notes HDF 2.1.2 release notes The documentation for doing an Ambari based upgrade to HDF 2.1.2 can be found here: HDF 2.1.2 Ambari based upgrade guide Thank you, Matt ... View more

@Bhagyashree Chandrashekhar NiFi at its core is aligned with any specific data format. NiFi can ingest data of any format (it is just treated as binary) The data is controlled in NiFi via a NiFi FlowFile. A FlowFile consist of Metadata about the actual content and the content itself. It si this FlowFile metadata that is the unit of transfer between processor components in a NiFi dataflow. When it comes to different available processor components, they may care about the content format if their job is to manipulate that content in anyway. I a m not familiar with EBCEDIC data, but form what i have read of EBCEDIC legacy file format is that it can be either EBCEDIC-Binary or EBCEDIC-ASCII. If the format is ASCII, you may be able to use processors like ReplaceText to manipulate the actual content. If it is binary, you may need to write your own custom NiFi processor component that would be able to process that data type. Or you might be able to use a one of NiFi's Scripting processors to use an external script to convert the format of these files to ASCII where you would then be able to modify them with existing processors. There are no EBCEDIC specific processor in NIFi as of now. Thank you, Matt ... View more

@Simon Jespersen If you cannot get this to work outside of NiFi, it is not going to work inside of NiFi either. But looking over your statement above, I see a couple things... 1. You are trying to use a "ppk" file. This is a Putty Private Key which is not going to be supported by SFTP. You should be using a private key in pem format. 2. SSH is very particular about permissions set on private keys. SSH will reject the key if the permissions are to open. Once you have you pem key make a copy of it for your NiFi application and make sure that copy is owned by the user running NiFi. The permissions also must be 600 on the private key. nifi.root 770 (-rwxrwx---) will not be accepted by SSH nifi.root 600 (-rw-------) will be accepted. You can't grant groups access to your private key. Thanks, Matt ... View more