On 30 Jan 2012, at 20:10, John Fereira wrote: > Actually, I *was* using SDB-1.3.4 *not* SDB01.3.3
Mystery solved.
> I was able to get your reconnector built and launch Fuseki with a
> configuration file similar to yours (but using MySQL instead of H2) but got
> empty results when issue a query. I had run into the same issue before and
> had to run a configuration that specified a UNION graph. Here's what my
> current configuration files looks like. With it, fuseki works for 8 hours
> (when the mysql wait_timeout is reached). I guess what I need is to figure
> out how to merge your fusekisdbreconnect class with a store that uses a UNION
> graph.
> <#sdb-part> rdf:type ja:RDFDataset ;
> # If ja:namedGraph is used here, there is no correspondence
> # with the name in the SDB store.
> ja:defaultGraph <#sdb-one-graph> ;
> .
>
> <#sdb-one-graph> a sdb:Model ;
> sdb:dataset <#dataset> ;
> sdb:graphName <urn:x-arq:UnionGraph> ;
> .
This was pretty long, but if I read correctly you're just trying to get a
dataset using the default union graph? That ought to be possible with SDB
directly but clearly isn't (no equivalent of the TDB assembler option).That
might cause performance issues for complex queries.
I've added this feature to my little hack:
<#dataset> rdf:type jumble:SDBConnect ;
sdb:layout "layout2/index" ;
jumble:defaultUnionGraph "true" ; # will switch option on globally, in fact
sdb:connection [
rdf:type sdb:SDBConnection ;
sdb:sdbType "h2:file" ;
sdb:sdbName "target/test-DB/H2" ;
]
.
Damian
signature.asc
Description: Message signed with OpenPGP using GPGMail
