Hi Tomek,
To start with I think a flat file based approach should be fine. While
working on [1] it was observed that 2M blobId consumed 500MB memory.
As this logic is to be implemented in oak-run probably it should be
fine for now to just use a in memory HashSet
Later if it becomes problem we
Hello,
I started working on OAK-3148, which is a new feature that allows to gradually
migrate blobs from one store to another, without turning off the instance. In
order to create the SplitBlobStore I need a way to remember (and save) already
transferred blob ids.
So, basically I need a
