Member since
04-24-2018
3
Posts
0
Kudos Received
0
Solutions
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
05-08-2019
06:59 PM
Hey Lee, did you figure something out with this. I am having the exact same issue on version 1.6.x . Thanks
... View more
04-24-2018
07:15 PM
Should the RPC URLs list multiple node? (i.e. http://nifi_node1:9091/nifi,http://nifi_node2:9091/nifi,http://nifi_node3:9091/nifi) Only reason i ask is that I have a simular set up for list/fetch S3 processors and noticed that it was all being processed via a single node even though i have a 3 node cluster. Thank you JF
... View more