Yes, problem solved. As always, thank you for the very quick response!
>________________________________ > From: Andy Seaborne <[email protected]> >To: [email protected] >Sent: Tuesday, June 25, 2013 3:50 PM >Subject: Re: unionDefaultGraph problem with Fuseki 0.2.8 > > >On 25/06/13 13:01, Andy Seaborne wrote: >> On 24/06/13 20:15, Elli Schwarz wrote: >>> I just downloaded the latest snapshot of Fuseki 0.2.8 this morning >>> (revision 1496155 from the trunk) . I'm using config-tdb-text.ttl, >>> (attached) which has tdb:unionDefaultGraph set to true. I start Fuseki >>> with: >>> >>> /usr/bin/java -Dlog4j.configuration=log4j.properties -Xmx3200M -jar >>> /opt/jena-2.10/jena-fuseki-0.2.8-SNAPSHOT/fuseki-server.jar --update >>> --config=config-tdb-text.ttl --port=3131 >>> >>> If I add any data to the triple store, whether I put it in a named graph >>> or not, and then attempt to query it without specifying a graph, I don't >>> get any results. >>> >>> If I query with this: >>> select * where { graph <urn:x-arq:UnionGraph> { ?s ?p ?o } } >>> I do get results, which implies that the unionDefaultGraph option I set >>> in my .ttl assembler isn't working correctly. >>> >>> Anyone have any ideas why the unionDefaultGraph capability isn't working? >>> >>> Thank you, >>> Elli >> >> Elli, >> >> Thanks for the report. I've recorded this as JENA-477. >> >> I think I understand what is (or in this case, is not) going on. It's a >> design issue in that the query is executing over the dataset abstraction >> for text datasets, and so not deciding to use the TDB execution engine >> at the right granularity. Fix in progress. > >Elli, > >Fuseki build #38 should have fixes in it for this (there are changes in >both ARQ and jena-text). Please let me know if it works as expected. > > > Andy > > > >
