Hi,
In my GTFS Fuseki endpoint I loaded the data set to the default graph
using tdbloader. Later I added two new graphs to the store with a
smaller set of data. This seems to work fine, I can address the triples
in each graph.
Now I would like to expose everything in the default graph for easier
On 17/06/15 21:24, Adrian Gschwend wrote:
Hi,
In my GTFS Fuseki endpoint I loaded the data set to the default graph
using tdbloader. Later I added two new graphs to the store with a
smaller set of data. This seems to work fine, I can address the triples
in each graph.
Now I would like to
Hi Andy,
How is everything going?
I am using another system to control the backup and restore process of
Fuseki. However an inconvenience is that I don't know the file name to
be used for the backup so I need to discover it manually. Is there a way
to get it from the JSON response?
In fact
Hi Andy,
Thanks for raising JENA-963 for me - I'll raise the issues directly in the
future. Sometimes it's hard to know whether things are intended (or at
least accepted) behaviours though.
Unfortunately I haven't got an exhaustive set of queries we need to
support; but we're basically hoping
When I execute a query with the s-query script, and -service is located on a
remote machine, I can observe that the load on the remote machine is very low,
while on the local machine fuseki consumes 100% of the cpu. The execution takes
a very long time, much more than when I execute s-query on
Discussion on dev@
On 16/06/15 13:29, Crapo, Andrew (GE Global Research) wrote:
Andy,
Did you run as Java Application? Run as Junit test, they will all show as
passed because Junit doesn't work for multi-threads.
Andrew
-Original Message-
From: Andy Seaborne [mailto:a...@apache.org]
On 17/06/15 10:16, Rick Moynihan wrote:
Hi Andy,
Thanks for raising JENA-963 for me - I'll raise the issues directly in the
future. Sometimes it's hard to know whether things are intended (or at
least accepted) behaviours though.
Point taken. It's those unfunded volunteers - can't rely on
On 17/06/15 15:12, Neubert, Joachim wrote:
An follow-up question: Is a
SERVICE http://localhost:3030/ds/query { ... }
clause within the query resolved as localhost = the local machine (where s-query is executed)
or localhost = the remote server (referenced in the --service argument to
An follow-up question: Is a
SERVICE http://localhost:3030/ds/query { ... }
clause within the query resolved as localhost = the local machine (where
s-query is executed) or localhost = the remote server (referenced in the
--service argument to s-query)?
Cheers, Joachim
-Ursprüngliche
