Hi!
On our Blazegraph instances (version 2.1.2) we investigated usage of features regarding
ordered values in solution sets. It is use case described within,
https://wiki.blazegraph.com/wiki/index.php/SPARQL_Update#Named_Solution_Sets
which is used for paging through data set.
We ran into problems with this. For sample data in attachment we made solution set with:
prefix ex: <https://example.org/>
prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>
prefix xml: <http://www.w3.org/XML/1998/namespace>
prefix xsd: <http://www.w3.org/2001/XMLSchema#>
INSERT INTO %entity_label
SELECT ?e ?e_l
WHERE {
SELECT ?e ?e_l
WHERE {
?e a ex:c .
?e rdfs:label ?e_l .
}
ORDER BY ?e
}
Hi! On our Blazegraph instances (version 2.1.2) we investigated usage of features regarding ordered values in solution sets. It is use case described within, https://wiki.blazegraph.com/wiki/index.php/SPARQL_Update#Named_Solution_Sets which is used for paging through data set. We ran into problems with this. For sample data in attachment we made solution set with:
and when queried with :
we get proper results which are:
but not always. We also get wrong data like
or else, from time to time.
Please, can you look at this problem? It breaks regular use case for above mentioned feature described in link.
Best regards, Adam data.zip