Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/98#discussion_r117082313
--- Diff: README.md ---
@@ -299,7 +299,19 @@ Additionally, users can utilize the MiNiFi Toolkit
Converter (version 0.0.1 - sc
if you do not want to enable client certificate base authorization
nifi.security.need.ClientAuth=false
-
+
+### Configuring Volatile and NO-OP Repositories
+
+ in minifi.properties
+
+ # For Volatile Repositories:
+ nifi.flow.repository.class.name=VolatileRepository
+ nifi.provenance.repository.class.name=VolatileRepository
+
+ # For NO-OP Repositories:
+ nifi.flow.repository.class.name=NoOpRepository
--- End diff --
My thought, initially was that we could have processors that could be self
contained and work with or without connections. In those cases the
configuration wouldn't need to be updated but we may be able to disable both
repositories at runtime thus altering certain devices to have a different
capability. I support what you are suggesting though but wonder if the Java
model fits all embedded devices and use cases.
---
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.
---
