On 18/06/15 16:49, Adrian Gschwend wrote:
Hi group,
I can't seem to understand the new structure of Fuseki 2.0 configuration.
In the documentation I read:
https://jena.apache.org/documentation/fuseki2/fuseki-configuration.html
"The directory FUSEKI_BASE/configuration/ with one data service
assembler per file (includes endpoint details and the dataset description.)
So I understand that as I create a file with the dataset configuration,
in my case I did this:
--
<#service2> rdf:type fuseki:Service ;
fuseki:name "/sbb" ; # http://host:port/da-ro
fuseki:serviceQuery "query" ; # SPARQL query service
fuseki:serviceReadGraphStore "data" ; # SPARQL Graph store
protocol (read only)
fuseki:dataset <#dataset> ;
<#dataset> rdf:type tdb:DatasetTDB ;
tdb:location "sbb" ;
# Query timeout on this dataset (1s, 1000 milliseconds)
ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000" ] ;
# Make the default graph be the union of all named graphs.
## tdb:unionDefaultGraph true ;
--
where the tdb for "sbb" is in run/databases
I called this file sbb.ttl, when I now start fuseki-server without
arguments I get:
ERROR Exception in initialization: Not found: sbb.ttl
When I create a full config file like in Fuseki 1.x I don't see the
dataset at all, even though it says in startup that it loads it. Config
looks like this:
http://pastebin.com/mZVKBp76
And it's loaded with the --config=config.ttl option
In the admin-interface there is no "sbb" dataset visible.
Any hints on what I'm doing wrong?
regards
Adrian
Hi Adrian,
Sorry for the delay.
Configuration works in two ways.
* The server is given a confuguation file on the command lien e.g.
"--conf config.ttl"
* Or it is in the FUSEKI_BASE area (configuration/)
There is also the database "system/" currently used to record UI-created
datasets/service but I'm considering chnaging it so the UI creates files
in configuration/.
On the command line, the configuration file is everything; server and
datasets. This is Fuseki1 style.
When it's using the run/ area, the sources are run/config.ttl (the
server setup), configuration/, one file per service+dataset and the
system database (like configuration/ but a database of named graphs, not
files).
The system database is slightly magic - it's tuned for smallness (direct
mode, small block size, small cache size - see tdb.cfg in it directory).
It isn't used in process a request - that's all in java objects for
the service registry.
> <#dataset> rdf:type tdb:DatasetTDB ;
> tdb:location "sbb" ;
> # Query timeout on this dataset (1s, 1000 milliseconds)
> ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000" ] ;
> # Make the default graph be the union of all named graphs.
> ## tdb:unionDefaultGraph true ;
> --
>
> where the tdb for "sbb" is in run/databases
>
> I called this file sbb.ttl, when I now start fuseki-server without
> arguments I get:
>
> ERROR Exception in initialization: Not found: sbb.ttl
I suspect it is a problem with base current directory. "sbb" will be a
relative file path from the current directory. Unfortunately that is a
bit exposed to how the server is being run, from a war file or the
standalone server. Which way are you running?
Firstly, try the latest snapshot - there was a fix (JENA-915) in this
are but I don't think it is just that for what you are seeing.
"run/databases/sbb" might work but it would be safest to use
"/whereever/run/databases/sbb".
This need cleaning up - it would be helpful to know which way you run
Fusek2 and which ways work.
Andy
