@Alexandros    You can accomplish this use ReplaceText with a more complex Java regular expression. The Replace Text is designed to replace every occurrence of the string matched by your java regular expression with the replacement value.  So you are probably seeing your replacement value inserted into your existing content twice. Try using the following java regular expression which will match your entire 3 lines of content: .*\n.*?(\d{2}.\d{4}).*?\n.*?(\d{2}.\d{4}).* Leave your replacement value as you already have it and make sure you have Evaluation mode still set to Entire text.   Hope this helps, Matt ... View more

@JamesE    You can handle this easily using a different set of Java Regular Expressions: .*action=(.*?) .* .*srcip=(.*?) .* .*timestamp=(.*?) .*   If it is possible that any one of these fields may be the very last field in the content line, for this to work you would need to append a blank space to the end of the content using the ReplaceText processor before sending your FlowFile to your ExtractText processor.  You need to have a blank space following each value so regex know where the value ends for each field. Your ReplaceText processor configuration would look like this: The "Replacement Value" is just a single space. Hope this helps, Matt ... View more

@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