[
https://issues.apache.org/jira/browse/NIFI-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792522#comment-17792522
]
Giovanni commented on NIFI-12442:
---------------------------------
Thanks for your considerations.
Surely the advantage is the speed of calculation. A data flow possibly enrich
data with half a million checks on 30 seconds with 2 clustered nodes (in my
private experience, with my local clustered components). It's way efficient
than other solutions. Obviously is up to the user to choose which one solution
fits better for its purpose. At FS space cost and possibly RAM (depending of
which RocksOptions the user choose), it could delivery a fast output.
I understand the problematic relative to the maintainability and compatibility
could be a problem.
As you said, it's probably a better solution to create an external library,
that receive constant updates, that a possible RocksDb chooser user could use.
Thank you, at this point I think that this Ticket could be closed.
> 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)
