|
If you were logged in you would be able to see more operations.
|
|
The native store's indexes currently do not flush out 'stale' data when triples are removed from the store. Although this typically is not a real problem (it does not significantly influence performance), it becomes noticable when significant amounts of data are removed: the indexes then become disproportionately large compared to the actual amount of triples stored (an actual case is a native store containing 80 million triples, having 3GB indexes, where 60 million triples were removed - the indexes stayed at 3GB however).
It should be possible to update the indexes and have them remove 'stale' entries to conserve disk space.
|
|
BTrees now reuse nodes that were discarded during removal operations and shrink the file when the last node in the file is removed (no node relocation yet).
|
|
Improvement
Closed
Minor
Native Store Indexes should update when removing triples