On 27/01/15 16:27, Stian Soiland-Reyes wrote:
On 27 January 2015 at 15:23, Andy Seaborne <[email protected]> wrote:
I didn't use tdbloader2 for now as it will only work with fresh databases (could add confusion to the README).
tdbloader does not do better when it's an existing, non-empty database. It avoids some transactional scaling issues but otherwise uploading to the server live is much the same.
Would I get reasonable defaults if I add a minimal config with just DatasetTDB, fuseki:dataset and tdb:location - or do I need to include all of those from the template?
Don't follow. config-tdb-dir is that minimal config isn't it? The templates take NAME and DIRectory. That's it.
The datasets created in the UI seem to live under system-configuration/ rather than in config.ttl
Yes - config.ttl is not updated by the server, just read. config.ttl is under user control.
-- should such a register-load shell script put things in there instead of config.ttl? Are those UUIDs registered somewhere?
The system database IIRC.
Q: Should I run the standalone Fuseki or a WAR inside say Tomcat?Your choice!I'll stick with the standalone then, as it means I get the tdb.loader for free :)Q: Are there any memory settings that should be made accessible?Heap - usually it does not need changing but if you have lots of datasets it might.I see - now it is this line: JVM_ARGS=${JVM_ARGS:--Xmx1200M} Why is this using ":" here? I don't understand that bit. :-)
as Rob says. And the "--" is really two different "-", one for the ":-", one for the "-Xm".
I guess I would need to freshen my sed skills to set the memory limit from a shell variable. So you generally mean.. a high number of datasets? Size of dataset or query doesn't matter much with TDB?Q: Is it safe to just stop fuseki-server with Ctrl-C / docker stop? It seems to stop a bit too fast, with no log outputs.Yes - or even "kill -9"Nice! So docker stop fuseki just works safely.The distribution has an unversioned file in it IIRCCould you clarify..? apache-jena-2.12.1.tar.gz and jena-fuseki-1.1.1-distribution.tar.gz don't seem to include fuseki2.
So I have to (at least until Fuseki 2.0.0 is released) download jena-fuseki-dist from https://repository.apache.org/content/groups/snapshots/org/apache/jena/jena-fuseki-dist/2.0.0-SNAPSHOT/ by finding the timestamp in https://repository.apache.org/content/groups/snapshots/org/apache/jena/jena-fuseki-dist/2.0.0-SNAPSHOT/maven-metadata.xml
There is a timestamp and an incremental count (ATM "21") jena-fuseki-dist-2.0.0-20150128.100051-21.zip Scroll down the list.(artifact may change jena-fuseki-dist => apache-jena-fuseki to agree with our style of delivery artifacts are "apache-jena-*")
Andy
