Andy Seaborne kirjoitti 16.11.2017 klo 22:04:
TDB1 or HDT.
TDB2 has no benefits for you at 40M triples at occasional updates.
Compaction would be a benefit, if it could be automated. But apparently
not in the current state (see today's dev@ thread).
TDB2 goals are to address the scale limitations on transactions, the
write-back queue overload problems, a better architecture e.g. fully
integrate in jena-text transactions, and no quirks about models across
transactions. TDB2 is experimental at this stage.
Understood.
(You could use DatasetGraphSwitchable in TDB2 to make a switchable HDT
backed database.)
Thanks for the tip!
I think there's a lot of potential in HDT, it's just hampered by
implementation bugs and lack of resources on the hdt-java side. For my
use case it would be almost perfect, but the hdt-java implementation
doesn't support union default graph functionality [1]. It could be added
of course, just hasn't been.
-Osma
[1] https://github.com/rdfhdt/hdt-java/issues/3
--
Osma Suominen
D.Sc. (Tech), Information Systems Specialist
National Library of Finland
P.O. Box 26 (Kaikukatu 4)
00014 HELSINGIN YLIOPISTO
Tel. +358 50 3199529
[email protected]
http://www.nationallibrary.fi
