On 29/08/15 15:39, Adrian Gschwend wrote:
On 25.08.15 14:06, Andy Seaborne wrote:
Hi Andy,
The problem is that the configuration of the "bfs" dataset is picked up
from the configuration database. Presumably you created it through the UI.
I did! Thanks a lot for the hint. Is this somewhere written in the
documentation? I know that I am not the only one who was running into
that, I've seen similar questions outside the mailinglist.
Putting it in the system database didn't turn out a good idea hence the
change at 2.3.0 (I can see now Fuseki would have to add editing
configuration file capabilities which would be nice but is distinctly
non-trivial).
What I still don't completely understand is why some people come across
this and not others. Makes writing useful document tricky!
Andy
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.
great tnx, will work with this one!
regards
Adrian
