Github user apiri commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/113#discussion_r122976076
--- Diff: README.md ---
@@ -302,17 +302,47 @@ Additionally, users can utilize the MiNiFi Toolkit
Converter (version 0.0.1 - sc
nifi.security.need.ClientAuth=false
### Configuring Volatile and NO-OP Repositories
-
+Each of the repositories can be configured to be volatile ( state kept in
memory and flushed
+ upon restart ) or persistent. Currently, the flow file and provenance
repositories can persist
+ to LevelDB. The content repository will persist to the local file system
if a volatile repo
+ is not configured.
+
+ To configure the repositories:
+
in minifi.properties
# For Volatile Repositories:
- nifi.flow.repository.class.name=VolatileRepository
- nifi.provenance.repository.class.name=VolatileRepository
+ nifi.flowfile.repository.class.name=VolatileFlowFileRepository
--- End diff --
Looks like this is still
[nifi.provenance.repository.class.name](https://github.com/apache/nifi-minifi-cpp/blob/master/libminifi/src/Configure.cpp#L34).
Totally fair game to update, but think we should make that change in
conjunction with this doc update.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
