...
These generated files contain serialized data about each of the JCR/Fedora nodes. Running the cURL command above, for example, generates binary files. The file names in the case of FileCacheStore are generated based on the hash of the node's UUID. For example, for root node, file -8.. gets generated, containing the node data. Although A hashing algorithm is used to map keys to buckets. The value files contain serialized ModeShape nodes. The key files can be read using org.infinispan.schematic.internal.document.BsonReader. (It does not seem possible to read these files using existing bson tools, like mongoDB bsondump, but further inspection is needed.) Although the generated file itself is binary, the data it contains can be read using a tool or ModeShape API. For example, for our root node, the data is:
...
Most of these files are binary and can be read by a LevelDB Java library.
FileCacheStore
As with the LevelDB option, when Fedora 4 is started with FileCacheStore configuration, ModeShape creates several directories on the filesystem:
- data
- expired
- index files
Specifying the FileCacheStore option would result in creating hundreds of binary files in that data directory (e.g. 11333332.. , -2334002.. etc)
Using the Infinispan 6.x deprecated FileCacheStore (specified via file/infinispan.xml, currently our ModeShape is on 5.x) results in creation of hundreds of binary files (compared to LevelDB). A hashing algorithm is used to map keys to buckets. The value files contain serialized ModeShape nodes. The key files can be read using org.infinispan.schematic.internal.document.BsonReader. (It does not seem possible to read these files using existing bson tools, like mongoDB bsondump, but further inspection is needed.)