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

Giovanni commented on NIFI-12442:
---------------------------------

Thanks David for answering this question. 
The use case that you proposed is exactly the one I was thinking of. Working on 
multiple nodes, data will be written and read in all nodes FS, maintaining 
databases consistency. 
A potential use case can be the one where a Rocksdb is created in a separate 
instance, loaded inside NiFi fs via S3, and read/updated via data flow, with 
updated data, and then re-uploaded to S3. This is a simple use case, where a 
user has total management power on his RocksDb. Then data inside them can be 
used to enrich data retrieved from the internet. 
As you said, this could probably not be much viable in the official repo. But 
can still be useful in certain cases.

> Adding support for RocksDB
> --------------------------
>
>                 Key: NIFI-12442
>                 URL: https://issues.apache.org/jira/browse/NIFI-12442
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.23.2
>            Reporter: Giovanni
>            Priority: Minor
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> I would like to suggest the creation of 3 new components:
> The first one is a service, which opens an existing RocksDb or, eventually, 
> using RocksOptions, create it from scratch. It will manage all the open 
> options (classic, read/write, only read, secondary).
> The second one, is a RocksDbReader, that uses the service to communicate with 
> the RocksDb in order to retrieve informations through a lookup. It can save 
> the searched content inside an attribute or inside the flowFile content. It 
> will be capable of using both APIs, such as simple "db.get" and via 
> RocksIterator.
> The last one, is a RocksDbWriter, that uses the same service as the reader, 
> but can write values inside the RocksDb, both from flowFile attribute or 
> flowFile content, using properties to determine the key to use.
>  
> Feel free to express your opinions, if you think this will be useful or 
> useless.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to