[
https://issues.apache.org/jira/browse/MINIFI-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103467#comment-16103467
]
ASF subversion and git services commented on MINIFI-249:
--------------------------------------------------------
Commit fe63485342fc0e84250887871826b9f17b1f9a94 in nifi-minifi-cpp's branch
refs/heads/master from Marc Parisi
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=fe63485 ]
MINIFI-249: Update prov repo to better abstract deser.
- Deserialization and serialization are better abstracted
into SerializableComponent allowing us to use all repos with
the same [de]serialization interfaces.
- Update Test resources to use local http server when possible
- Allow for different volatile configurations
- Update removals and link FlowFileRepo to content repo
MINIFI-330: convert const char* to std::string
This closes #110.
Signed-off-by: Aldrin Piri <ald...@apache.org>
> 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
> Fix For: cpp-0.3.0
>
>
> 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)
