[Bigdata-developers] Federated queries from BlazeGraph instances use BINDINGS instead of VALUES

[Jerven T. B. <Jer...@is...>]

Hi BlazeGraph developers,

The SPARQL BlazeGraph generates to send to other endpoints in response 
to a SERVICE call use the non standard BINDINGS keyword instead of the 
finally accepted values clause.

I believe this can be fixed with the patch below.

This was raised by users of the sparql.uniprot.org endpoint who want to 
use data in their blazegraph in combination with our virtuoso instance 
guarded by a sesame layer.

Regards,
Jerven


index c44a626..8000b3d 100644
--- 
a/bigdata-rdf/src/java/com/bigdata/rdf/sparql/ast/service/RemoteSparql11QueryBuilder.java
+++ 
b/bigdata-rdf/src/java/com/bigdata/rdf/sparql/ast/service/RemoteSparql11QueryBuilder.java
@@ -293,7 +293,7 @@ public class RemoteSparql11QueryBuilder implements 
IRemoteSparqlQueryBuilder {
// Variables in a known stable order.
final LinkedHashSet<String> vars = getDistinctVars(bindingSets);

-            sb.append("BINDINGS");
+            sb.append("VALUES");^M

// Variable declarations.
{

-- 
Jerven Tjalling Bolleman
SIB | Swiss Institute of Bioinformatics
CMU - 1, rue Michel Servet - 1211 Geneva 4
t: +41 22 379 58 85 - f: +41 22 379 58 58
Jer...@is... - http://www.isb-sib.ch