@mikecolux Can you include a screenshot of how the List/FetchSFTP processors are configured?   ... View more

@jasonjojo   Check out trycloudera.com...   These are trials for CDP Public Cloud which will give you a great chance to see what the new Cloudera looks like.   TL;DR; its not hadoop anymore. ... View more

Below is a blog post for a flow i made using the nifi api, which will accept a template (XML), load the template, get template, then follow chain of api calls to get the appropriate flow definiton file (JSON). https://cldr-steven-matison.github.io/blog/dataflow-xml-to-json/   The concepts you need to understand are demonstrated with invokeHttp to execute the sample calls. Check the nifi api docs.  You can do these calls with curl, etc., but i chose to do them in nifi.   Be mindful that to start using the api from outside of nifi,  you need to be following the initial api call for an access token to be used with the rest of the calls.  ... View more

@DataEngineer07  This seems like something external interrupting this process (ie:InterruptedException). I would try a separate nifi instance with updated version to test basic connectivty to Azure Event Hub.   That will confirm if its something specific to that original host or nifi version/config.  Considering the port difference you notice, i would also investigate that on the affected host as well (proxy or other).   ... View more

@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