Re: Redundant data store when using BekeleyDB as he storage backend?
Dmitry Kovalev <dk.g...@...>
toggle quoted message Show quoted text
I don't think anybody here will be able to confirm specifically if your observations are correct or not without a specific reproducible example.
However I think I have a possible explanation of why you are seeing more data stored than you expect. When you commit a graph transaction adding and edge or a vertex, Janusgraph may actually write to multiple backend stores, depending on configuration:
- vertex store (the actual data)
- index store (update the index for searching, essentially duplicating the value of indexed property)
- transaction log store (can be used for replication etc)
- id block store to manage id block allocation
Some of these stores (e.g. transaction log), as you may guess from the names, are write-only i.e. they only can grow.
On Monday, 16 December 2019 13:09:56 UTC, br...@... wrote: