On 12/10/14 14:50, baran_H wrote:
On Sun, 12 Oct 2014 15:25:44 +0200, John A. Fereira <[email protected]>
wrote:
I'm not familiar with Openshift but in order to figure out what the
problem might be we'll need to know what version of Fuseki is being
used and see a copy of the configuration file. Just a shot in the
dark, but it sounds like it could be related to the configuration and
the use of defaultUnionGraph.
We've been using fuseki for a couple of years in a production
environment and it's worked well for us.
not that i thought that something is wrong with Fuseki or Openshift is a
production environment, but can you give me a link and a sample-query
string, am a bit curious, that is all..
thanks, baran
John has identified the issue. It's running with defaultUnionGraph --
updates will go into the real default graph, but be invisible to the
query default graph.
How do I know?
I tried:
SELECT * { GRAPH <urn:x-arq:DefaultGraph> { ?s ?p ?o } } LIMIT 1
and got a result row.
The real, storage default graph as a pseudo URI (not included as a named
graph) so you can get to the storage default graph even with
It's running version 0.2.7
--------------------
David - you may be interested in Fuseki2. It has security; there is a
much better UI; there is a WAR file so you have more deployment options.
http://jena.staging.apache.org/documentation/fuseki2/
(NB - this is the documentation staging site).
Andy
