Located Triples

[Qup42]

SPARQL 1.1 Update. The Graph Management Operations are dependent on #1337 and not supported yet.

Status

It should somewhat work. You can try out some queries like

1. Insert triples

INSERT DATA {
  <http://wallscope.co.uk/resource/olympics/athlete/MeganOlwenDevenishTaylorMandevilleEllis> <foo> <baz>
}

or

PREFIX foaf: <http://xmlns.com/foaf/0.1/>
INSERT {
  ?a <foo> <baz>
} WHERE {
  ?a foaf:gender <http://wallscope.co.uk/resource/olympics/gender/F> .
}

2. Retrieve triples

SELECT * WHERE {
  <http://wallscope.co.uk/resource/olympics/athlete/MeganOlwenDevenishTaylorMandevilleEllis> ?b ?c 
}

or

SELECT * WHERE {
  ?a <foo> <baz>
}

TODOs:

• Split up into smaller chunks for PRs
  • LocatedTriple
  • DeltaTriple
  • integration
• Unit Tests
  • CompressedRelationReader -> together with integration PR
  • DeltaTriples -> WIP
• Better feedback of processing time for to guide future (optimization) decisions

[Qup42]

Some data:

• Built with Release CMake Profile against cfc581e
• Executed on my Laptop (AMD Ryzen 7840U, 32GB RAM, SSD)
• Olympics dataset
  • ~400k and ~8M triples are to be located, once each for deletion and insertion
  • times are averaged over all permutations

~400k

	IdTable, random-access	IdTable, pre-sorting	std::vector, random-access	std::vector pre-sorting
Result materialisation	70ms	70ms	70ms	70ms
Sorting	N/A	60ms-160ms	N/A	20ms
Location	15ms-20ms	10ms-20ms	15ms-20ms	10ms-20ms

~8M

	IdTable, random-access	IdTable, pre-sorting	std::vector, random-access	std::vector pre-sorting
Result materialisation	1330ms	1330ms	1330ms	1330ms
Sorting	N/A	1500ms-4000ms	N/A	460ms-510ms
Location	330ms-450ms	240ms-360ms	330ms-460ms	220ms-350ms

[sonarcloud]

Quality Gate passed

Issues
21 New issues
5 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud