You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mr TheSegfault (JIRA)" <ji...@apache.org> on 2019/06/07 11:39:00 UTC

[jira] [Commented] (MINIFICPP-550) Create RocksDB Controller Service

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

Mr TheSegfault commented on MINIFICPP-550:
------------------------------------------

[~bakaid] Am I mistaken that this is something you'd be interested in tackling? This is something that is a new feature to be available to all components – First and foremost as a cache ( sort of like NiFi ) but also to give us the ability to store information that can be persisted in ways that are similar to what we have for variable registry or the upcoming parameters work. The controller service aspect would make this required to be part of the flow, but we should also have a generalized access mechanism that facilitates a registry that will be used for local access. 

> Create RocksDB Controller Service
> ---------------------------------
>
>                 Key: MINIFICPP-550
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-550
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: Bug
>            Reporter: Mr TheSegfault
>            Assignee: Daniel Bakai
>            Priority: Major
>             Fix For: 0.7.0
>
>
> A RocksDB Controller service will give us the ability to store arbitrary information into controller services that can later be sent via SiteToSite. This will support many of my monitoring and test use cases. Using RocksDB as  a key/value store we can serialize and send this information periodically



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)