Thankyou Steven 🙂 ... View more

@VijaySankar    Unfortunately with the information you have shared, it is not possible for me to validate what the issue is here. I would need to output from the openssl commands i shared earlier to help. openssl s_client -connect <server hostname>:<server port> Also the verbose listing of both your keystore and truststore files would be needed:   keytool -v -list -keystore keystore.jks keytool -v -list -keystore nifi.com.jks     The target server is what decides if connection is going to use mutual auth or not.  The invokeHTTP is the client side of this connection and only provides what the server asks for in the server hello response.   It is possible also in that server hello response that the server wants a client certificate; however, the list of CAs sent in that server hello response does not contain a CA capable of trusting your clientAuth PrivateKeyEntry in your nifi.com.jks.  In that case client would not send the client certificate since server is incapable of trusting it. Matt ... View more

I’m the schema remove the second row in fields.  So it’s just id1.   Now do a test: use generateflowfile with the schema in contents.  Then evaluatejson.  In this processor click +, and make id1.  The value for id1 is then $.value.id1 (this is the code to get the real value.  Then route evaluatejson routes to an output port.  Run.  Inspect the item in the queue and confirm you see the attribute id1.   This is a simple example to help you understand how json works, how to get the data from the value object, how to confirm schema is correct, and how to unit test by looking at flowfile in the queue. ... View more

@saivenkatg55    Your Out Of Memory (OOM) issue is occurring in the NiFi toolkit script and not in NiFi itself.  Ambari will execute the NiFi toolkit before the NiFi service itself is ever started.  If the NiFi toolkit fails, Ambari does not proceed any further. I can see you are running HDF 3.2.0 which exposes the heap memory settings under the NiFi configs in Ambari: Locate the above line and increase your heap settings here.  Once the toolkit script finished running which must occur before NiFi is even started, that JVM is gone.  So the memory allocation set here are short lived and will not impact available memory for your NiFi. Hope this helps, Matt   ... View more

You should be able to accept your own reply as solution marking it closed/solved.   One thing I do notice, which I HIGHLY recommend against is using "localhost"...   ... View more

I am going to test it here myself shortly.  I have a use case where we are inserting ISO-8601 into Elastic where data ultimately also goes to exernal csv table (wi thout the timestamp).  I should be able to quickly validate what is required for a working example.   I suspect you are having issues with the after ss parts matching the serde syntax. ... View more

Thank you for your amazing advice and your support is highly appreciated. ... View more

Thanks Steven, I removed the hostname and it started working after I set hostname box empty. ... View more

@stevenmatison: Sure , i got your point.   Csv Reader and Putdatabase Config are given below:     Sample of content of Flowfile before putdatabase is as below:   TIME,CAUSE,CATEGORY,PREVIOUSCOUNT,CURRENTCOUNT,AVERAGE,SEVERITY 2020-01-10 20:10:00,UNABLE TO COMPLY,DIAMETER: Permanent Failure,1172,1150,686,MAJOR 2020-01-10 20:10:00,Unspecified,NAS,15071,15240,13533,MINOR.   Thanks for replying. ... View more

@murali2425 You could build a nifi flow that could “copy” files to guthub.  This would need to be done by creating a custom processor or maybe even just ExecuteScript to run a custom python script.    Either route you take you would need to make sure that all nifi nodes are setup with permissions to write to the github repo.  Then inside of your custom processor or script you would execute the required git commands to commit (“copy”) the file(s). ... View more