Github user brosander commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/115#discussion_r123744302
--- Diff: README.md ---
@@ -326,26 +326,44 @@ Additionally, users can utilize the MiNiFi Toolkit
Converter (version 0.0.1 - sc
### Http Configuration Listener
- Http Configuration Listener will pull flow file configuration from the
remote command control server,
+ Http Configuration Listener will pull flow file configuration from the
remote command control server,
validate and apply the new flow configuration
- in minifi.properties
+ in minifi.properties
nifi.configuration.listener.type=http
nifi.configuration.listener.http.url=https://localhost:8080
- nifi.configuration.listener.pull.interval=1 sec
+ nifi.configuration.listener.pull.interval=1 sec
nifi.configuration.listener.client.ca.certificate=./conf/nifi-cert.pem
if you want to enable client certificate
nifi.configuration.listener.need.ClientAuth=true
nifi.configuration.listener.client.certificate=./conf/client.pem
nifi.configuration.listener.client.private.key=./conf/client.key
nifi.configuration.listener.client.pass.phrase=./conf/password
-
+
+### UID generation
+
+MiNiFi need to generate many unique identifiers in the course of
operations. There are a few different uid implementations available that can
be configured in minifi-uid.properties.
+
+Implementation for uid generation can be selected using the
uid.implementation property values:
+1. time - use uuid_generate_time
+2. random - use uuid_generate_random
+3. uuid_default - use uuid_generate (will attempt to use
uuid_generate_random and fall back to uuid_generate_time if no high quality
randomness is available)
--- End diff --
Well, uuid_generate_time is a lot faster than the random version but it
leaks information about which node and what time the uuid originate from, I
thought that might be relevant info if there are privacy-conscious applications
of MiNiFi.
https://linux.die.net/man/3/uuid_generate_time
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
