From: Kjetil Kjernsmo
Date: Thu, 28 May 2009 10:03:42 +0200
On Wednesday 27 May 2009 18:08:38 Hugh Williams wrote:
> Currently the only timeout that can be specified is as a parameter to
> a query against the SPARQL endpoint , as "&timeout=" for example:
Surely, this will not
Kjetil,
On 28 May 2009, at 09:03, Kjetil Kjernsmo wrote:
On Wednesday 27 May 2009 18:08:38 Hugh Williams wrote:
Currently the only timeout that can be specified is as a parameter to
a query against the SPARQL endpoint , as "&timeout=" for
example:
Surely, this will not override an upper l
On Wednesday 27 May 2009 18:08:38 Hugh Williams wrote:
> Currently the only timeout that can be specified is as a parameter to
> a query against the SPARQL endpoint , as "&timeout=" for example:
Surely, this will not override an upper limit set by the server administrator?
Kind regards
Kjetil
Hi Alan,
Currently the only timeout that can be specified is as a parameter to
a query against the SPARQL endpoint , as "&timeout=" for example:
http://demo.openlinksw.com/sparql?default-graph-uri=http%3A%2F%
2Fdemo.openlinksw.com%2Fdataspace%2Fperson%2Fdemo&should-
sponge=&query=select+di
Is there a way to control the various time limits set on a query (such as
MaxQueryCostEstimationTime or MaxQueryExecutionTime) from the SPARQL
endpoint? Perhaps by prefixing the query with a 'DEFINE', or perhaps by
adding a additional parameter to the query URI?
(And BTW, is there documentation s
