@rizalt It's hard to talk to a solution here without a lot more details (version of stack, ambari, java, etc).  That said,  some of the hits I find against this error are from 2017(many years ago).  There is a great risk to operate Ambari as it is no longer supported and available within the Cloudera ecosystem.       I would recommend you evaluate modern solutions (CDP) for the same stack of services you are familar with in Ambari. ... View more

@RobertusAgung  I am not familiar with metabase specifically, but i would start with the most modern cloudera jdbc driver:   https://www.cloudera.com/downloads/connectors/impala/jdbc/2-6-15.html   ... View more

@Naveen_Sagar  I am not sure if this is the right solution, but if you are using NiFI itself to communicate with its own NiFi API,  you can skip the authorization token completely as NiFi is already authorized to execute its own API calls. ... View more

@alan18080   It seems this may be related to Process Group within a Process Group ( a known bug), but its hard to know based only on this error.   You may find more verbose information in the nifi log which will help better resolve.   Here is one solution for the same:   https://community.cloudera.com/t5/Support-Questions/quot-No-Flow-Exists-quot-When-Importing-Process-Groups-with/m-p/241006   ... View more

Excellent work here Oleksandr!!   ... View more

@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