@dan_lucas  Not much to go on here, but it seems like you are having some issues resolving the networking for host/hostnames and ports.  Particularly:  myip3/<unresolved>:11443   You may want to work on providing true host names and ips and trying nifi again. ... View more

@bou7miiiz are you setting the mime type in the post HEADERS from nifi to the api? The 415 error seems to be expecting "application/json".   Add this property the same way you added Authorization. ... View more

@ZorteK This is certainly an interesting scenario.   First thing i would wonder is why there is 1 out 10000 that is different.  If that is not something you can remove, then you will not able able to apply the same schema to all parts.   Its possible this is a bug with the CHOICE, but im not sure or familiar with that.   Few solutions here:  1 check for and handle the exception in a separate flow branch able to parse that second schema.   Or you can run the entire flow where the GEO value is a full string.  Do not try to parse it down to finite schema within that string.   ... View more

Ofcourse we can help.  Just make a new post.  Try to include as much detail as possible, screenshots, how you have invokeHttp configured, errors, etc.   In your new post tag me using the @ with my username "steven-matison". ... View more

This is awesome!   ... View more

@edim2525   I have never had a concern to replicate kafka with nifi keeping exact order.    Perhaps others can respond with more details in a nifi context. That said,  my customers are using Streams Replication Manager (SRM) for heavy duty kafka replications.     https://docs.cloudera.com/cdf-datahub/7.2.16/howto-streams-replication-manager.html https://docs.cloudera.com/runtime/7.2.16/srm-overview/topics/srm-replication-overview.html There are several different form factors of SRM across private and public cloud but the doc links above should give you a good idea of what it is.   ... View more

@SAMSAL Thank you.     For future reference.  If you ever need to figure out what the request is,  simply use NIFI UI to do the action you want while monitoring your Developer Tools.   This will expose the full request/response on any given UI action. I have filed a JIRA for this. https://issues.apache.org/jira/browse/NIFI-12503 ... View more

You need to send a flowfile to InvokeHttp that has the content you want.   Make this flow to test:  GenerateFlowfile (body of flowfile is the JSON payload), route to InvokeHttp.  Your post headers are added to InvokeHttp in similar manner as to how you did "Body Content". ... View more

@Fayza  Without seeing any error it is impossible for us to solve a specific problem.   That said, I have some suggestions. 1.  Always make sure you have a working api call. For example: Use Postman.  You need to 100% know the call is working, auth, headers, proper format, proper payload, etc.  This also makes sure the receiving end is open (networking, firewall, etc). 2.  Test invokteHTTP without routing fail,retry,no-retry back to the processor.  I use an output port for everything other than response.  In testing, you need to know what happened.  Inspect flowfile attributes inside of fail,retry, no-retry, to get more details. When i know my flow works, i may auto terminate, or re-route failure back to processor again, but NOT during testing/creation of the flow. 3.  Last but not least, make sure that nifi host(s) are able to reach the endpoint.  I suspect this is the issue you are bumping into.     If you get invokeHttp talking to the endpoint, you should be seeing more details as to what if any errors are in the mutation payload.    ... View more