@Tokolosk I would recommend that you provide java's cacerts as the keystore/truststore with the default password (changeit).  This will work for most public certs.    If you have a custom cert at the SFTP end you will need to import that cert and create your own keystore/truststore.  I always try cacerts first. ... View more

Hi @DennisJaheruddi    I managed to speak to some devs on Slack and we found a related issue, posted below.   https://issues.apache.org/jira/projects/NIFI/issues/NIFI-8749   Hopefully it gets fixed soon so that we can upgrade to 1.14.0 +  ... View more

The only fix I've found so far is to update the Record Reader of this processor: * Make sure it is not inferred * Write the schema with the order of the record fields matching the order of the table fields.   I'm not sure if there was a reason this was changed or of this is a bug? ... View more

Just to add to the above, I am getting a lot of the below errors. All the devices sending data via http POSTS are on cellular networks with some having bad signal. Could this be causing the difference between posts the HandleHttpRequest processor receives vs the amount of flowfiles it creates?   ERROR POST from HandleHttpRequest[id=da9f6288-5359-38e9-cb70-1c832b186f63] Failed to receive content from HTTP Request from 10.0.2.2 due to java.util.concurrent.TimeoutException: Idle timeout expired: 60000/60000 ms: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 60000/60000 ms   Sorry about the bump but I'm really struggling to get to the bottom of this. ... View more

If you have multiple data sources then you can create a processor for each and have them aggregate in a central processor/group. In the picture below we have 6 different data sources (API's, FTP's, etc), each in its own processor group. Within their respective groups they reformat the data so that it is uniform and send it on its way.   I had to blank out some text but this should give you the idea.      ... View more

Consequent to this we found that some of our devices has a newline character to the url they sent, e.g. instead of posting to   http://my.url   they would post to   http://my.url\n   When using Wireshark we could see http 404 errors with http://my.url%0A   The \n came from a mistake and removing it has stopped all the errors.   I'm interested to know if anyone has any insight into why this causes and error and how to mitigate this if possible (just as a fail-safe). ... View more

Hi Pe, just wondering if you came right with your question. I'm on the same boat and being new to certificates this is rather a deep dig to find the answer.  ... View more

Hi Steven,   I used @bingo 's solution to get Nifi to find my JAVA_HOME.   But you mention that Nifi does not need this to run. Do you know what is the impact for running nifi without it knowing where Java is installed? ... View more