Member since
09-29-2015
871
Posts
723
Kudos Received
255
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3367 | 12-03-2018 02:26 PM | |
2316 | 10-16-2018 01:37 PM | |
3633 | 10-03-2018 06:34 PM | |
2408 | 09-05-2018 07:44 PM | |
1834 | 09-05-2018 07:31 PM |
07-25-2016
03:51 PM
In general many users can share the same instance (these are not the same as OS users). In the NiFi 0.x baseline (HDF 1.2) users can have roles and roles can restrict what users can do. For example, a monitor can get a read only view of the UI and a data flow manager can change anything they want. In NiFi 1.x (HDF 2.0, not yet released) there will be a much finer grained security model where policies can be created for anything on the canvas to give specific users or groups access to an individual component (processor, process-group, etc.). A keytab is a file on the operating system controlled by the standard operating system file permissions. If the NiFi process is running as an operating system user that can access that keytab file, then any NiFi user can go into the UI and create a PutHDFS processor and type in the path to that keytab, because its not based on the user accessing NiFi, its based on the OS user NiFi is running as. The only way I could see preventing this was if files/keytabs could be defined as some kind of first-class resource in NiFi, and then policies could be created to limit which NiFi users could use those resources.
... View more
07-21-2016
06:54 PM
If the NiFi process has access to keytab1 and keytab2 on the filesystem, then any use can enter either of those keytabs into a processor. You would need two separate NiFi instances each running as a different operating system user, lets say user1 and user2, and user1 only has filesystem access to keytab1, and user2 only has filesystem access to keytab2. You can run NiFi as a user other than root by specifying a value for the run.as property in bootstrap.conf.
... View more
07-21-2016
06:43 PM
2 Kudos
The boostrap process restarts NiFi when the main NiFi process dies. An easy test is to start a new NiFi and then kill -9 the main process and you'll immediately see it come back with a new pid. OOM would probably be tricky because a lot of times the Java process does not die when encountering an OOM and sticks around in some bad state.
... View more
07-19-2016
07:00 PM
It is in the 0.7.0 release, part of the stanadard bundle: https://github.com/apache/nifi/blob/0.x/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/JoltTransformJSON.java
... View more
07-19-2016
05:42 PM
I don't think mapreduce-site.xml is being used by PutHDFS... I mean of course you can specify it as one of the config resources and NiFi will read it into a Hadoop Configuration object, but I don't think any mapreduce properties are involved in reading/writing to HDFS. Can you try exporting LD_LIBRARY_PATH in the shell where you will start NiFi from?
... View more
07-19-2016
01:36 PM
Did you try setting the LD_LIBRARY_PATH as described above?
... View more
07-18-2016
09:06 PM
4 Kudos
Currently there aren't any processors that perform direct manipulation of Avro, although we definitely would like to have some. Possible options to work around this...
Use ConvertAvroToJson followed by the new JOLT transform processor followed by ConvertJsonToAvro (involves a lot of conversion and may lose some of the initial schema) Use ExecuteScript processor to manipulate the Avro (I am not sure if any of NiFi's supported scripting languages have good Avro support) Write a custom Java processor to manipulate the Avro (https://cwiki.apache.org/confluence/display/NIFI/Maven+Projects+for+Extensions) Happy to help answer any questions if going the custom Java processor route.
... View more
07-18-2016
03:39 PM
Are you sure that NiFi can reach all the services in EMR (HBase, ZK, etc)? Also, can you look in nifi_home/logs/nifi-app.log and see if there is a full strack-trace that goes with that error. If so it would be helpful to see that, thanks.
... View more
07-18-2016
02:10 PM
1 Kudo
Usually if you have NiFi running on a node that is not part of the HDFS/HBase cluster, you copy the appropriate config files (hbase-site.xml and core-site.xml) to the NiFi node.
... View more
07-12-2016
02:06 PM
3 Kudos
This example uses site-to-site to send logs from one instance to another using a push model: https://github.com/bbende/nifi-streaming-examples The first instance has a Remote Process Group pointing to the URL of the second instance. The second instance has an Input Port to receive logs, which the Remote Process Group from the first instance is connected to. You also need to enable nifi.remote.input.socket.port and nifi.remote.input.secure on the node where the an incoming connection will be made. In this example that is the node with the Input Port which will receive an incoming connection from the Remote Process Group on the first node.
... View more