@moshell281   This is indeed a very tough solution to solve.   The only thing that comes to mind is creating your own schema, versus inferring the schema.  Creating that schema from scratch could be a long task.  So one trick you can do would be to run the flow to infer the schema, and configure the controller service to write that schema to an attribute.   Inspect a flowfile and grab that schema.   Next modify the schema to suit your needs, and then modify and test the flow with the specified schema (no longer inferred).   This should allow you control to specify the correct data type for "000" so it is not assumed to be "0". ... View more

@ehehtenandayo your Hive Metastore URI should look like "thirft://<Hive Metastore host>:9083."   Note that hive meta store host is not the same as the hive server host.   You can usually locate the correct thrift string in the hive-site.xml as such: <property> <name>hive.metastore.uris</name> <value>thrift://host1.cloudera.site:9083,thrift://host2.cloudera.site:9083</value> </property>   ... View more

Appreciate the positive feedback, but i differ to @MattWho.  He had already reached out on your behalf.      This is beauty of the community here, we are all friends working toward common goals.  :high five: To be clear,  2.0 is not officially ready for prime time,  so you need to be careful with expectations and vigilant with your own evaluation and testing.      You also need to be ready with process to upgrade to the next version(s) as they come out.        ... View more

@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