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
04-24-2018
08:57 PM
1 Kudo
@Jose
Gonzalez You can specify more then one host but it is not required. Once the RPG establish a connection to the target host it will retrieve the S2S details of the target cluster and store that locally. If the host you provided become unavailable at anytime after that initial connection , it will try anyone of the other nodes it learned about previously to get S2S details. Having multiple nodes configured helps when NiFi by giving the source Nifi more then one target node to establish initial connection with. - Your load-balancing issue is completely unrelated to how many nodes URLS you configured in your RPG. Here is an article that covers how load-balancing works with an RPG: https://community.hortonworks.com/content/kbentry/109629/how-to-achieve-better-load-balancing-using-nifis-s.html - Thanks, Matt
... View more