@Maciej Michalec i found a related article https://issues.apache.org/jira/browse/NIFIREG-209 - Support rebuilding metadata DB from Git repo. with thanks to @Michal Klempa who created a working docker image "https://hub.docker.com/r/michalklempa/nifi-registry" the Fix was released as part of version 0.4.0 (May 21, 2019) ... View more

You are right, it is just a label issue in the HDF mack extention ... View more

@choppadandi vamshi krishna and @Geoffrey Shelton Okot, you should load the mpack HDF (or create your own), this will extend HDP with NiFi v1.7 / NiFi Reg v0.2, if you want NiFi version 1.8 then you will need to adjust ambari resources in the mpack folder structure to extend HDP with NiFi v 1.8 ... View more

Hi @Julio Gazeta please take a look at this code sample using-counters-in-apache-nifi " The best way to define and update counters is to use ExecuteScript processor with the following piece of Groovy code: " ... View more

HI @Adi Jabkowsky i found the following post "data-encryption-on-hive-table-using-ranger-kms" this document describes a kms/spark/hive data flow. i also know that ranger can restrict user access to a column and masking the data in a few ways. a good guide can be found here. apache-ranger-and-hive-column-level-security hope this helps ... View more

Hi @Ajay Sachdev, like @Harald Berghoff points out overall volume is less relevant, to provide a better picture we need to know estimated throughput and an estimate of what processors you want to use in the flow. As each of the operation will require mem/io ... View more

Hi, @Abhinav Joshi are you sure you set the C2 Server port to be 8080, the default is 10080 besides that all looks to be fine, if it still does not work please share the snippets from your config ... View more

Hi @Abinav Joshi If you mean in miNiFi, you need to set the bootstrap to point to the C2 Server and set the class # Query string to pull configurations with (no version), "<yourflowname/templatename>" has to match exactly nifi.minifi.notifier.ingestors.pull.http.query=class=<yourflowname/templatename> authorizations and authorizers.xml would be a whole new topic, as it will deal with who can do what after sign-in ... View more

If you want to use the http ingestor update the miNiFi ./conf/bootstrap.conf (C2 section "nifi.minifi.notifier") update ./conf/minifi-c2-context.xml point the beam to the NiFi server that will hold the templates. Each ingestor has it own constructor. create/import the template in NiFi now start the c2 server and test "http://c2-server:10080/c2/config?class=iot-minifi-raspberry-agent&version=1" this should return the config.yml now when you start miNiFi you will see in the logs that after a short interval miNiFi comes to live. the how to in my first answer describes a step by step setup ... View more