Hello Andy,
[tdbloader2 performance for 1B+ triples]
On Mon, Jul 30, 2012 at 05:06:55PM +0100, Andy Seaborne wrote:
How big are the node* files (node2id.dat, .idn, nodes.dat) in the
resulting database in this case?
node2id.dat 9470738432 bytes
9,470,738,432 = 9G
node2id.idn 50331648
Hello Andy,
On Sun, Jul 29, 2012 at 09:28:47PM +0100, Andy Seaborne wrote:
(A) problem found : timezones with non-zero minutes.
Recorded as JENA-287
Fixed - data on disk is not affected. It was a bug in reconstructing
the date time.
Thank you again!
Will there be a new Jena release soon
On 07/08/12 11:30, Michael Brunnbauer wrote:
Hello Andy,
On Sun, Jul 29, 2012 at 09:28:47PM +0100, Andy Seaborne wrote:
(A) problem found : timezones with non-zero minutes.
Recorded as JENA-287
Fixed - data on disk is not affected. It was a bug in reconstructing
the date time.
Thank you
On 30/07/12 13:33, Michael Brunnbauer wrote:
Hello Andy,
On Sun, Jul 29, 2012 at 05:22:57PM +0100, Andy Seaborne wrote:
How big are the node* files (node2id.dat, .idn, nodes.dat) in the
resulting database in this case?
node2id.dat 9470738432 bytes
9,470,738,432 = 9G
node2id.idn 50331648
I've put some debugging in so that the term being unpacked it printed out.
It looks like it is the timezone.
Andy
On 24/07/12 12:13, Michael Brunnbauer wrote:
Hello Andy,
On Thu, Jun 14, 2012 at 01:12:25PM +0100, Andy Seaborne wrote:
I guess it would be a good idea to look at the
On 24/07/12 12:24, Michael Brunnbauer wrote:
Hello Andy,
On Tue, Jul 24, 2012 at 01:13:59PM +0200, Michael Brunnbauer wrote:
BTW: Here is some output from tdbloader2 for this TDB which shows that
the tdbloader2 data phase runtime gets quite non-linear for very big datasets.
I called
On 29/07/12 17:05, Andy Seaborne wrote:
I've put some debugging in so that the term being unpacked it printed out.
It looks like it is the timezone.
Andy
(A) problem found : timezones with non-zero minutes.
Recorded as JENA-287
Andy
On 24/07/12 12:13, Michael Brunnbauer
On 29/07/12 17:34, Andy Seaborne wrote:
On 29/07/12 17:05, Andy Seaborne wrote:
I've put some debugging in so that the term being unpacked it printed
out.
It looks like it is the timezone.
Andy
(A) problem found : timezones with non-zero minutes.
Recorded as JENA-287
Fixed - data on
On 13/06/12 15:18, Michael Brunnbauer wrote:
Hello Andy,
On Wed, Jun 13, 2012 at 03:01:20PM +0100, Andy Seaborne wrote:
com.hp.hpl.jena.tdb.store.DateTimeNode.unpackDateTime(DateTimeNode.java:169)
I don't recognize the error (and the line numbers are 0.8.10 so don't
align with
On 13/06/12 06:46, Michael Brunnbauer wrote:
hi all
I have another question: Can I run tdbdump on a TDB used by Joseki as long as
I do not cause any SPARQL updates via Joseki ?
No.
Fuseki has a facility to run a backup (live) while running.
POST to
Hello Andy,
On Wed, Jun 13, 2012 at 12:54:18PM +0100, Andy Seaborne wrote:
Can I run tdbdump on a TDB used by Joseki as long as
I do not cause any SPARQL updates via Joseki ?
No.
I anticipated that and ran tdbdump (from TDB-0.8.10) while Joseki was not
running. Does the Exception I posted
Hello Andy,
On Wed, Jun 13, 2012 at 03:01:20PM +0100, Andy Seaborne wrote:
com.hp.hpl.jena.tdb.store.DateTimeNode.unpackDateTime(DateTimeNode.java:169)
I don't recognize the error (and the line numbers are 0.8.10 so don't
align with development).
It looks like a weird dateTime -
hi all
I am trying to dump a big TDB and got this exception after most of it was
dumped. Is the TDB corrupt or is there an error in the output code ?
Exception in thread main org.openjena.atlas.AtlasException: formatInt:
overflow
at
13 matches
Mail list logo
