Hi, I found this about insert operation and parallelism: Note: The INSERT ... VALUES technique is not suitable for loading large quantities of data into HDFS-based tables, because the insert operations cannot be parallelized, and each one produces a separate data file. Use it for setting up small dimension tables or tiny amounts of data for experimenting with SQL syntax, or with HBase tables. Do not use it for large ETL jobs or benchmark tests for load operations. Do not run scripts with thousands of INSERT ... VALUES statements that insert a single row each time. If you do run INSERT ... VALUES operations to load data into a staging table as one stage in an ETL pipeline, include multiple row values if possible within each VALUES clause, and use a separate database to make cleanup easier if the operation does produce many tiny files. http://www.cloudera.com/documentation/enterprise/5-5-x/topics/impala_insert.html ... View more

step1 : remove the authorization.xml from all the nodes rm /var/lib/nifi/conf/authorizations.xml step2 : update node identities in advanced_nifi_ambari_ssl_configuration section with <property name="Node Identity 1">CN=hostname1, OU=XXXXX</property> ... for all the nodes (make sure you remove comment tags in XML). step3 : restart the NiFi service found that authorizations.xml is not being update after first generation, hence this is causing the problem. ... View more

@Bryan Bende I appreciate the help immensely will get back to you on Monday with feedback. Cheers to a good weekend! ... View more

Hello Matt, Thanks for clarifying. So, no need to report... ... View more

@Bryan Bende thanks a lot for the help works perfect. I attached a snippet of the updated workflow should anyone experience such an issue in the future.Thanks again. ... View more

It would probably be best to start a new question for this, but... If you have three different CAs that were used to generate three different certs for each of your standalone nodes, then you will need to create a single truststore that has the public keys of all three CAs, and each NiFi node will need to use that trutstore in order to trust the other nodes. The initial admin identity must be the same on all nodes. If you have a client cert that worked on one of your standalone nodes, and if you do what I described above with the truststore, then you can still use this client cert. Each node, will need all the node identities listed. You will also need to delete the users.xml and authorizations.xml from each node so that it starts over. ... View more

How do you not use Zookeeper for service discovery. Please give me step by step instructions if possible. Tried all recommended methods online with no luck. Thank you. ... View more

Hi All, even i too need one simple example how to set mail alerts with business logic when something went wrong in NIFI. if possible share one sample link. I am very new to NIFI, now i need this requirement to my current support project, Thanks in advance. ... View more

No problem, glad it was helpful 🙂 If you are reaching the login screen, then it means your browser is not forwarding your credentials to NiFi. You could try setting the negotiate properties to just "myhost.de" instead of the full url with port. Another thing to look at might be the domain being used by your KDC... In this example I was using nifi.apache.org as the domain, so I had to add a mapping in /etc/hosts to map nifi.apache.org to localhost so I could use nifi.apache.org in my browser to access my local NiFi. If you are accessing myhost.de to get to your NiFi instance, but that isn't the domain in your KDC, then it won't line up and probably won't forward your credentials. ... View more

Thanks ! that was helpful . I don't see anywhere "Accept" ... View more