Steve Judkins wrote:
This week I’m evaluating Virtuoso in shared web hosting environments.
The two environments I’m planning on evaluating are OpenSolaris
Containers (from Joyent) and Linux Virtual Private Servers (from
Slicehost). A entry priced Slice usually starts at 256Mb RAM and
Hi Jens,
Can you provide copy or the URL to download the geonames dataset you
are trying to load ? A copy of your virtuoso.log file would be
usedful to have in case their are any additional messages reported
that may be related. As stated initially this is an old procedure
Fred used
Hello,
Hugh Williams wrote:
Hi Jens,
Can you provide copy or the URL to download the geonames dataset you are
trying to load ?
I send the dump URL to you in private mail (non-public).
A copy of your virtuoso.log file would be usedful to
have in case their are any additional messages
Hi Jens,
Strange. Try sparqling the endpoint to get triples from resources
defined after this one: 6690544
That way we will know if it continues to index the file.
If not, then I think I would kill the instance, check what is the last
resource being indexed (last checkpoint), split the
Hello Tim,
Tim Haynes wrote:
Jens Lehmann wrote:
Is there an easy way to query the number of triples in a graph
(http://geonames.org) or the whole triple store? That way I could see
how many there are and whether this number changes.
sparql SELECT count(*) from http://geonames.org WHERE
Jens Lehmann wrote:
Hello Tim,
Tim Haynes wrote:
Jens Lehmann wrote:
Is there an easy way to query the number of triples in a graph
(http://geonames.org) or the whole triple store? That way I could see
how many there are and whether this number changes.
sparql SELECT count(*)
Jens Lehmann wrote:
Hello Tim,
Tim Haynes wrote:
Jens Lehmann wrote:
Is there an easy way to query the number of triples in a graph
(http://geonames.org) or the whole triple store? That way I could see
how many there are and whether this number changes.
sparql SELECT count(*)
On 29-Oct-08, at 3:48 AM, Hugh Williams wrote:
The other point to check is that you are using the specific Virtuoso
JDBC Driver (virtjdbc3.jar) shipped with your release.
This was exactly the problem. I'm developing in Eclipse, and the
project referenced a library that contained an older
Hi Luke,
Good to hear this is working for you now ...
Was the reference to the old virtjdbc3.jar something you had added to
your project or was this part of the Eclipse product you are using ?
Best Regards
Hugh Williams
Professional Services
OpenLink Software
Web: http://www.openlinksw.com
