d.run(Thread.java:829)
Cheers, Joachim
> -Ursprüngliche Nachricht-
> Von: Andy Seaborne
> Gesendet: Montag, 14. Februar 2022 13:46
> An: users@jena.apache.org
> Betreff: Re: AW: AW: AW: AW: xloader "Can't find gzip program"
>
>
>
> On 14/02/202
or somethign else?
--
My experience is that gz is faster to load.
bz2 emphases compactness over speed.
Andy
Cheers, Joachim
-Ursprüngliche Nachricht-
Von: Andy Seaborne
Gesendet: Samstag, 12. Februar 2022 11:15
An: users@jena.apache.org
Betreff: Re: AW: AW: AW: xloader "Can't
. Februar 2022 11:15
> An: users@jena.apache.org
> Betreff: Re: AW: AW: AW: xloader "Can't find gzip program"
>
> Hi Joachim,
>
> Aside: I've realised why the timestampes are fixed at "2022-01-30 15:03".
>
> The build setup is for repeatable builds o
Hi Joachim,
Aside: I've realised why the timestampes are fixed at "2022-01-30 15:03".
The build setup is for repeatable builds of releases. Any build from the
X.Y.Z release source, with the same JDK, will generate the byte-wise
same jar files.
Each release build fixes the timestamp and uses
Sorry, my fault: I've actually had jena-4.4.0 active, not 4.5.0-SNAPSHOT.
Now the loading works smoothly:
22:50:10 INFO Load node table = 62 seconds
22:50:10 INFO Load ingest data = 37 seconds
22:50:10 INFO Build index SPO = 7 seconds
22:50:10 INFO Build index POS = 12 seconds
22:50:10
