nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MINIFI-37) Native Volatile Content Repository implementation
Date Wed, 24 May 2017 13:25:04 GMT

    [ https://issues.apache.org/jira/browse/MINIFI-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022884#comment-16022884
] 

ASF subversion and git services commented on MINIFI-37:
-------------------------------------------------------

Commit d26d65af4448ddb054975601a9bf59f8660e6a8d 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=d26d65a ]

MINIFI-37: Create a volatile repository and config items for
NoOp and Volatile repository configuration

Allow the max count of the volatile repository size to be configurable

This closes #98.

Signed-off-by: Aldrin Piri <aldrin@apache.org>


> Native Volatile Content Repository implementation
> -------------------------------------------------
>
>                 Key: MINIFI-37
>                 URL: https://issues.apache.org/jira/browse/MINIFI-37
>             Project: Apache NiFi MiNiFi
>          Issue Type: Task
>          Components: C++, Core Framework
>            Reporter: Aldrin Piri
>            Assignee: marco polo
>            Priority: Minor
>              Labels: native
>
> Given the constrained environments in which MiNiFi could operate, it would be beneficial
to provide a content repository that is strictly in memory for those environments where disk
storage may be limited or non-existent. 
> This implementation should consider configuration options around its footprint such as
number of entries held and/or sheer capacity.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message