This is by design. Nothing in the spec says it must only make one query per SERVICE call and ARQ takes the approach which is often more efficient of substituting bound values into the SERVICE calls and making multiple more specific calls.
This also has the side effect of actually doing more what the user intended. Often remote services have result limits on them therefore making a generic query may not return any relevant data that joins with the rest of the query even if the remote dataset does contain such data. On the other hand making multiple specific queries tends to find the data the user actually wanted. Rob On 14/02/2014 04:44, "Kamalraj Jairam" <[email protected]> wrote: >Hello All, > >I¹m having performance issues with ARQ federated query. > >ARQ seems to generate multiple select queries to the endpoints when it >should just send only 2 queries to the respective endpoints > >CONSTRUCT { ?s ?p ?o . ?s ><http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ><http://localhost/target#Doctor> .} >WHERE { SERVICE <http://localhost:8084/processor/webresources/rs/sparql> >{ ?s ?p ?o } SERVICE ><http://localhost:8084/processor/webresources/rs/sparql> { ?s ?p ?o . ?s ><http://www.w3.org/1999/02/22-rdf-syntax-ns#type> ><http://localhost/traleerdf/db#Physician> } } > >What am i doing wrong? > >regards > >Regards, > >Kamalraj Jairam >General Manager - Solutions Development >Semantic Software >www.semanticsoftware.com.au<http://www.semanticsoftware.com.au/> >Australian Office: +61-2-9931-7848 >Australian Cell: +61-405-203134 > > >
