[
https://issues.apache.org/jira/browse/NIFI-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795080#comment-17795080
]
Giovanni edited comment on NIFI-12442 at 12/10/23 1:59 PM:
-----------------------------------------------------------
Dear David,
As you suggested, I've implemented the DistributedMapCacheClient interface,
while still keeping the old components within the project.
There's a pre-release version, feel free to try it.
When creating the services, you can add dynamic properties to add RocksOptions
to the RocksDb instance. I suggest you to use the option: "setCreateIfMissing",
"true", to create automatically the RocksDb instance if not existing.
I'm up to other suggestions. Soon I'll release it to maven central.
Here's the link to the pre-release with the NAR file in it:
[Pre-release
v1.0.1|https://github.com/kommpn/nifi-rocksdb-manager/releases/tag/v1.0.1]
was (Author: JIRAUSER301883):
Dear David,
As you suggested, I've implemented the DistributedMapCacheClient interface,
while still keeping the old components within the project.
There's a pre-release version, feel free to try it.
When creating the services, you can add dynamic properties to add RocksOptions
to the RocksDb instance. I suggest you to use the option: "setCreateIfMissing",
"true", to create automatically the RocksDb instance if not existing.
I'm up to other suggestions. Soon I'll release it to maven central.
Here's the link to the pre-release:
[Pre-release
v1.0.1|https://github.com/kommpn/nifi-rocksdb-manager/releases/tag/v1.0.1]
> 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)
