You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mike Thomsen (Jira)" <ji...@apache.org> on 2022/03/29 22:30:00 UTC

[jira] [Resolved] (NIFI-1172) SimpleCache processor

     [ https://issues.apache.org/jira/browse/NIFI-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Thomsen resolved NIFI-1172.
--------------------------------
    Resolution: Not A Problem

The way I read the ticket, it looks like Fetch/PutDistributedMapCache provide this functionality.

> SimpleCache processor
> ---------------------
>
>                 Key: NIFI-1172
>                 URL: https://issues.apache.org/jira/browse/NIFI-1172
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Toivo Adams
>            Priority: Minor
>
> We have cache controller services. 
> Also we have plans to implement State Management.
> https://cwiki.apache.org/confluence/display/NIFI/State+Management
> Both are very useful for implementing standard and custom processors.
> But maybe SimpleCache processor out of the box is also useful?
> Consider “Database Lookup Approach” from user mailing list (14-15 nov)
> SimpleCache has 2 different inputs. 
> One is for request/lookup some value by key.
> Second is update and accept key and value.
> First request/lookup is invoked. If value is in the cache, Success output will have value.
> If not Retrieve output will contain info for query. We connect Query processor to this relationship.
> Query processor Success output will be connected back to SimpleCache input for update cache operation after successful query.
> SimpleCache can be implemented using LevelDB.
> LevelDB is very fast when all data fits in memory. And at the same time supports writing data to disk for bigger amount of data.
> Thanks
> Toivo



--
This message was sent by Atlassian Jira
(v8.20.1#820001)