@I_Mesh01 This error is stating that your topic schema and flink schema do not match.   I cant see much above related to the shape of the data or the schema, but this is what you should be looking at.   Conflict in data/column types, missing data, etc, will result in the deserialization errors. ... View more

@hegdemahendra   This instability is usually a result of the cluster's tuning and/or workload greater than cluster tunning and spec can sustain for long period of time.   When you restart the cluster, you are effectively resetting the memory allocation.   If you are restarting the entire nifi server(s), then you are giving a fresh operating system just like rebooting windows if its running slow.  Things will work fine again until cross the fine line between working and not working. Before restart, and making tuning steps, you should document the state of the system when it is not responding as expected.  What is the load on each node?  What is the used/vs available memory? etc.   Next you should investigate Garbage Collection. ... View more

@matdulgi The drivers are able to be downloaded from public internet and you are able to use them accordingly.   https://www.cloudera.com/downloads/connectors/impala/odbc/2-7-0.html https://www.cloudera.com/downloads/connectors/impala/jdbc/2-6-32.html.html     ... View more

CHeck out this link @joseomjr shared in another post:   https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1   And here is a great blog from Pierre Villard:   https://medium.com/cloudera-inc/getting-ready-for-apache-nifi-2-0-5a5e6a67f450     Nifi 2.0 brings python native, where jython was very limited library set. ... View more

@ckumar is Correct.   For large volume ingestion into the receiving host, you need a maria db host that can handle 1000s of transactions per second.   Nifi can easily exceed default configurations for total connections.   With a well tuned highly available mariadb,  you can crank up execution time and concurrency on nifi and get 10,000s+ transactions per second. ... View more

@MR_KD  You should have a look in the Ranger audit logs for Result: Denied.  Then begin to add the appropriate ranger policies.  The denial should explicitly show the rule that was violated.  Additionally, you may need to create the hdfs location, and or fix permissions if it exists already and has the incorrect permissions. ... View more

@joseomjr Is on to the right solution here.  Your regex statement should match "kafka.topic" not "${kafka.topic}".     A quick test in regex101.com confirms "kafka\.topic" should match. ... View more

@raj_dev This may be a better question to the OSS NiFi Community.  There is a mailing list and Slack (chat) you can find here: https://nifi.apache.org/mailing_lists.html At Cloudera we provide our own branded NIFI UI.  You would need to do similar.  This is a very complicated task that requires that you build your own binaries w/ the modifications to the UI. Before you go so deep as to build a new UI w/ your logo, be sure to have a look at Nifi of the Future, where you deploy nifi flows as a function in any cloud provider, or nifi on kubernetes.  In this future state no one sees or touches the nifi UI.  You can find more about Cloudera DataFlow here: https://docs.cloudera.com/dataflow/cloud/index.html     ... View more