Hi Peter,
Has this failure to load the conductor just started occurring as I
assume you have been using this log_enable option for sometime now ?
Are you performing these inserts using the Conductor SPARQL UI to
perform your inserts or is a separate program being used for this ?
Also, are
Note.
The manual approach works but, again, each construct'ed TTL is only 1
million triples long.
There is a limit as well.
Why not add some new procedures to the RDF toolset?
On Sun, Aug 9, 2009 at 7:30 PM, Aldo Bucchi wrote:
> Hi,
>
> This is a common usecase and I have seen it appear over and
Hi,
This is a common usecase and I have seen it appear over and over ( in
different forms and shapes ).
The objective is to copy all triples in a are remote graph into a
local graph. The remote graph is accessible via SPARQL.
1. Getting the data from the remote end
On the remote SPARQL endpoint
Hi all,
In order to debug my last issue I decided to log into the isql console and turn
trace_on
There were no messages at all that seemed to be relevant to the last error but
there was a strange message related to something else. The following message is
the bug
08:57:27 COMP_2 SPARQL 127.0.
Hi all,
I am using a particular server for a large number of constant and concurrent
SPARUL INSERT's and it seems that it has broken itself somehow because the
conductor doesn't show anymore. The SPARQL interface and INSERTS and
CONSTRUCT's are still actually working but it is still worrying th
