On 18.06.15 00:55, Andy Seaborne wrote: Hi Andy,
> This is TDB? yes > If your turn unionDefaultGraph on, then the stored default graph is not > visible in a query (it can be accessed via a special graph name that is > not included in the union of named graphs) so I'd expect it to be > inaccessible. ah ok, interestingly the data in the default graph I still see. > If you are not seeing the default graph as the union of the two named > graphs, then something is amiss with the setup. How are you setting > unionDefaultGraph? (and which version of code are you running?) I use a Docker image of Fuseki 2.0, in particular https://registry.hub.docker.com/u/stain/jena-fuseki/ I've configured my TDB like this: <#sbbtdb> rdf:type tdb:DatasetTDB ; tdb:location "sbb" ; # Make the default graph be the union of all named graphs. tdb:unionDefaultGraph true ; # Query timeout on this dataset (1s, 1000 milliseconds) ja:context [ ja:cxtName "arq:queryTimeout" ; ja:cxtValue "1000" ] ; . After that I restarted the docker. I will see if the config is really read by turning off the configured endpoint for a try. > unionDefaultGraph works (in TDB) by using the quad indexes and ignoring > the G part; e.g. it get SPO from SPOG (and reducing any duplicates to > get set semantics). ok that makes sense thanks. > You'll have to load a named graph with data to see it in the default > union graph. ok so when I use tdbloader I need to provide a graph name. FYI the second two graphs I loaded to the store via the new web interface of Fuseki after that. regards Adrian
