Member since
08-21-2018
11
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2929 | 08-23-2018 04:49 AM |
05-08-2019
08:56 PM
Lee, all, We tracked down the issue to an attribute variable I was using to put into the json. It had unescaped/hidden characters (\n) that where causing the JOLT processor to fail; however like you, it would work via the "Advance Editor". I used escapeJson() on the attribute it works it also makes the \n are visible in the flowfile. https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#escapejson Simple Example: [ { "operation": "default", "spec": { "content": "${ext_content:escapeJson()}", <- ext_content attribute contained the issue "date": "${ext_date}", "updateDate": "${ext_updateDate}" } } ] Hope this this helps and saves someone else some time! JF
... View more
08-23-2018
04:49 AM
1 Kudo
I have solved the problem.
It was simple issue but all new to this and none of the examples online show this fix.
First you need to have a keystore and there is a link above on creating one of those.
Then this is what was missed you need to download the certificate from the site providing the data.
echo -n | openssl s_client -connect newsapi.org:443 | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > /tmp/examplecert.crt Then import to your keystore sudo keytool -import -keystore truststore.jks -file /tmp/examplecer.crt -alias <sitename> Then set up the Control Service Device for the StandardSSLContextService
... View more