What's the best way of implementing a chronicle map where the value side is a map or a set?
I need data structures similar to the following where I can store multiple versions of some data with a specific id:
chronicle-map: String -> Map<String,V>
$id -> {v0-> value-v0, v1-> value-v1, v2 -> value-v2}
or possibly two maps:
chronicle-map-1: String -> Set<String>
key-$id -> Set{v0,v1,v2}
chronicle-map-2: String -> V
version-$id-v0 -> value-v0
version-$id-v1 -> value-v1
version-$id-v2 -> value-v2
(Atomicity and serialisation performance are my main concerns). acquireUsingLocked/getUsingLocked
methods don't seem to work with standard map/set implementations.