On 16/01/12 18:14, Eric Scott wrote:
On 01/15/2012 09:28 AM, Andy Seaborne wrote:
That needs investigating - it should work. It looks like it might be
connected to Audun's report "Problem persisting N-Triples" as this
erroneous behaviour is characteristic of unflushed caches.
Could you tell me what
fuseki-server --version
reports?
> fuseki-server --version
Jena: VERSION: 2.6.4
Jena: BUILD_DATE: 2010-12-12T16:56:15+0000
ARQ: VERSION: 2.8.9-SNAPSHOT
ARQ: BUILD_DATE: 2011-09-14T21:54:22+0100
TDB: VERSION: 0.8.11-SNAPSHOT
TDB: BUILD_DATE: 2011-09-04T18:10:31+0100
Fuseki: VERSION: 0.2.1-SNAPSHOT
Fuseki: BUILD_DATE: 2011-09-15T08:18:13+0100
Could you also say what's in the configuration file?
Here is what I think is the relevant excerpt:
<#server> rdf:type fuseki:Server ;
fuseki:services
(...
<#aboutCongressService>
...
)
.
<#aboutCongressService>
rdf:type fuseki:Service ;
rdfs:label "Service for congressional data from rdfabout.com";
fuseki:name "aboutCongress";
fuseki:serviceQuery "query"; #enables <form
action="[service]/query">...</form> in html
fuseki:serviceUpdate "update"; #enables <form
action="[service]/update">...<form> in html when fuseki-server is called
with --update option.
fuseki:serviceUpload "upload"; #Non-sparql upload service.
fuseki:serviceReadWriteGraphStore "data"; # enables s-put
fuseki:dataset <#aboutCongress_dataset>;
.
<#aboutCongress_dataset> rdf:type ja:RDFDataset;
ja:defaultGraph <#aboutCongress_graph>
.
<#aboutCongress_graph> rdf:type tdb:GraphTDB;
rdfs:label "Data about members of congress from aboutRdf.com";
tdb:location "/home/escott/TDB/congress"
It is much better to directly connect the TDB dataset to the service.
If the TDB-backed graph is inside a general (in-memory) dataset wrapper,
not a TDB dataset, then update sync is not going to work reliably.
<#aboutCongress_dataset> rdf:type tdb:DatasetTDB ;
tdb:location "/home/escott/TDB/congress" ;
.
Andy
.
On 14/01/12 20:32, Eric Scott wrote:
I'm playing with Fuseki using a config file:
fuseki-server --config <config-file> --update dataset
Where <config-file> declares several services, all of which have
associated tdb files.
When I use:
s-update --file <sparql-file> --service
http://localhost:3030/myService/update
The update works just fine, but update does not persist if I kill the
fuseki-server and restart with the same arguments. I note that several
files within the associated TDB directory have updated timestamps, but
querying against the new inserts produces an empty result set.
Are there config options or something else one needs to provide in order
to ensure such persistence?
