codecov[bot]
commented
2 weeks ago Codecov Report
Attention: Patch coverage is 89.06250% with 14 lines in your changes missing coverage. Please review.
Project coverage is 89.16%. Comparing base (
bb70c4a) to head (d70705b). Report is 1 commits behind head on master.
Additional details and impacted files
```diff @@ Coverage Diff @@ ## master #1603 +/- ## ========================================== - Coverage 89.17% 89.16% -0.01% ========================================== Files 372 372 Lines 34579 34635 +56 Branches 3912 3912 ========================================== + Hits 30835 30883 +48 - Misses 2471 2479 +8 Partials 1273 1273 ```:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Qup42
sparql-conformance[bot]
sonarcloud[bot]
joka921
The already existing
DeltaTriplesclass maintains a dynamically changing set of insertions and deletions relative to the original input data, together with a (single) local vocab. The class is not threadsafe and has to be used with care. In particular, concurrent update queries have to be serialized, and while a query makes use of the "delta triples", it has to be made sure that they are not changed over the course of the processing of that query.Both of these problems are solved by the new
DeltaTriplesManagerclass. The index has a single object of this class. It maintains a singleDeltaTriplesobject, write access to which is strictly serialized. Each new query gets a so-called snapshot of the current delta triples. This is a full copy (of the delta triples located in each of the permutations and of the local vocab). These snapshots are read-only and multiple queries can share the same snapshot. A snapshot lives as long as one query using it is still being processed.