[
https://issues.apache.org/jira/browse/MINIFI-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056677#comment-16056677
]
ASF GitHub Bot commented on MINIFI-249:
---------------------------------------
Github user phrocker commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/110
@benqiu2016
1) Yes, I have run for two days. Have also run valgrind to show no memory
leaks
2) Yes, and in this case I would encourage the users to use the file
system based repositories. The benefit to using the volatile repo is that we
don't need to use the file system API ( and potentially context switches) . It
may be advantageous to create a file stream that uses mmap instead of open.
> Volatile Provenance Repository
> ------------------------------
>
> Key: MINIFI-249
> URL: https://issues.apache.org/jira/browse/MINIFI-249
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
> Components: C++, Core Framework
> Reporter: Aldrin Piri
> Assignee: marco polo
>
> It would be helpful to have a volatile implementation for handling
> provenance. While the data guarantees of capturing/storing information work
> in some scenarios, in others, folks may wish to just hold data while the
> instance is running. This is predicated on an extensible interface that
> supports this configurability.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
