@JamesE  This is easy enough do using the splitContent processor: for the "Byte Sequence" property simply hit your spacebar to set a single space. If you found this answer addressed your question, please take a moment to accept to resolve this thread.   Hope this helps, Matt ... View more

@Former Member  Since you are asking a new question unrelated to the question asked in the original subject, I kindly ask that you start a new question.  Would be happy to help.  Asking multiple questions in one thread makes a thread harder to follow for other users of this community forum. If you feel this question subject has been answered, please accept a solution provided to close out this thread. Thank you, Matt ... View more

@Boenu    You will need to configure your HandleHttpRequest processor with a SSL Context Service in order to encrypt data in transit being sent to this processor from a client.  This of course then means you client needs to be able to at a minimum to trust the server certificate presented by this SSL context service in the TLS handshake.  The truststore you use in the NiFi SSL Context Service will only need to contain the public cert for your client or complete certificate trust chain for your client if you have configured your HandleHttpRequest processor to "Need authentication" in the Client Authentication property.  Mutual Authentication is not needed to ensure encryption of data in transit.   Hope this helps, Matt ... View more

@JSJ    Let's assume you have following directory structure: /nifi/test/AX1/ /nifi/test/AX2/ /nifi/test/XY1/ /nifi/test/XY2/ You would configure your listFile processor as follows: Hope this helps, Matt ... View more

@fowler7878    You are correct that MonitorActivity can not be used to monitor on activity based on per month thresholds. Your use case is not one NiFi is designed to handle.  NiFi is designed to work with FlowFiles and typically NiFi processor are not designed to return directory listings. Your use case may require you to build your own custom NiFi processor or perhaps your own custom script that your can execute via ExecuteStreamCommand or ExecuteScript processors where the script returns number of files in a target directory which you can then make notification routing decisions with. I was just trying to offers a builtin solution/suggestion while not exactly what you are looking for.   Thank you, Matt ... View more

@kam1  Processors are not coded to expose the exceptions to the FlowFile. Typically how this handled is by Using the SiteToSIteBulletinReportingTask.   Anytime a component throws an exception the processor will display a bulletin in the upper right corner and that same bulletin will be sent to the bulletin board.  The same exception along with stack trace (if there is one) is also logged to the nifi-app.log. The S2SBulletinReportingTasks allows you to capture all produced bulletins and send them via S2S to another NiFi or even back to same NiFi to be processed as FlowFiles for notification and alerting reasons through a dataflow. Writing exceptions out to FlowFile attributes would be problematic for following reasons: 1. FlowFile attributes exist in NiFi heap memory and exceptions can be large. 2. A FlowFile may pass multiple processor which produce bulletin/exception. Is expectation we overwrite previous exception with new exception?  Or create a new FlowFile attribute based on processor uuid for each exception encounter during life of FlowFile? This leads back to point 1 issue. It is better to handle exceptions as content within their own FlowFiles via the reporting task mentioned above.   Hope this helps, Matt ... View more