Hi Adrian,
The problem is that the configuration of the "bfs" dataset is picked up
from the configuration database. Presumably you created it through the UI.
That has an assembler that has a timeout of 3000ms for that dataset.
In Fuseki v2.3.0, UI created databases don't go into the system database
any more - they go into run/configuration/ as turtle so they are easier
to edit.
You can either edit, with SPARQL Update, the system database or,
simpler, delete the system database entirely (it only had one assembler
in it) and put a file in run/configuration/.
There is one for bfs below I used in testing, with your database
location in it.. It also has all the unnecessary initialization stuff
removed that is no longer needed for Fuseki 2.3 + TDB. After all, Fuseki
itself uses TDB so TDB setup and writing for assemblers happens anyway.
Andy
---- configuration/bfs.ttl -----------------------
@prefix : <http://base/#> .
@prefix tdb: <http://jena.hpl.hp.com/2008/tdb#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix fuseki: <http://jena.apache.org/fuseki#> .
:service_tdb_all rdf:type fuseki:Service ;
rdfs:label "TDB bfs" ;
fuseki:name "bfs" ;
fuseki:serviceQuery "query" ;
fuseki:serviceQuery "sparql" ;
fuseki:serviceReadGraphStore "get" ;
fuseki:serviceReadWriteGraphStore "data" ;
fuseki:serviceUpdate "update" ;
fuseki:serviceUpload "upload" ;
fuseki:dataset :tdb_dataset_readwrite
.
:tdb_dataset_readwrite rdf:type tdb:DatasetTDB ;
tdb:location
"/Users/ktk/workspace/zazuko.bfs/fuseki/run/databases/bfs" ;
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000" ] ;
.
On 25/08/15 08:31, Andy Seaborne wrote:
Hi Adrian,
I've downloaded the file successfully and wil look at the issue as soon
as I can.
Andy
On 24/08/15 18:55, Adrian Gschwend wrote:
On 24.08.15 13:05, Andy Seaborne wrote:
Hi Andy,
Adrian - That would be perfect. I don't think I need the data, just
the setup. It would also be useful to know exactly how you are
making the call. A per-query timeout is possible with the header
"Timeout:" or parameter &timeout=.
I use this curl command to execute it:
curl -H "Accept: application/n-triples" --data-urlencode
query@construct/map_municipality2classes.sparql
http://localhost:3030/bfs/sparql -o out/map_municipality2classes.nt
Didn't check the exact header sent though.
It'll be OK - curl does not add anything relevant.
I've tared everything including the data, it's just 14MB compressed.
Execute fuseki-server within the "fuseki" subdirectory, the shell-script
fuseki-construct.sh fires a bunch of construct queries into "out"
directory.
http://ktk.netlabs.org/misc/fuseki-timeout.tar.bz2
Note that the one I mention above is commented-out right now in this
shell script.
regards
Adrian
