-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Understanding documentation, loading and creating datasets #33
Comments
Aiming for persistence of data, I do not understand the meant use of the Two scenarios: (one) if I load data immediately after # start anew from scratch
docker ps -a
# CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# no container is running
docker run --name fuseki-data -v /fuseki busybox # data container
docker run --name fuseki-loadsh-use-fuseki-data \
--publish 3030:3030 -e ADMIN_PASSWORD=pw123 \
--volumes-from fuseki-data \
--volume /home/aplank/sandbox/staging:/staging \
stain/jena-fuseki \
./load.sh cetaf-test Thread-1_herbarium.bgbm.org.rdf
# ERROR Does not exist: /fuseki/databases/cetaf-test/ So I guess I have to create a Scenario two: docker run --name fuseki-data -v /fuseki busybox # data container
docker run --name fuseki-app --detach --publish 3030:3030 \
-e ADMIN_PASSWORD=pw123 --volumes-from fuseki-data \
stain/jena-fuseki
docker logs fuseki-app # look fine
docker stop fuseki-app
docker ps --all
# CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
# 35f00de23352 stain/jena-fuseki "/docker-entrypoint.…" About a minute ago Exited (137) 18 seconds ago fuseki-app
# b5e5195b55ea busybox "sh" 5 minutes ago Exited (0) 5 minutes ago fuseki-data
# import RDF data to a brand new data base cetaf-test
docker run --name fuseki-loadsh-use-fuseki-data \
--volumes-from fuseki-data \
-v /home/aplank/sandbox/staging:/staging \
stain/jena-fuseki \
./load.sh cetaf-test Thread-1_herbarium.bgbm.org.rdf
# works so far but what shall I do with container fuseki-loadsh-use-fuseki-data ?
I did in scenario two:
In this example, then what?
What scenario is meant to function for persistence of data? Here I would like you to provide a minimum example that works in itself. Can you provide it please or point me to my mistakes? Thank you |
I found that the error … Manually you can fix the missing # go into the running container fuseki-app (it has only primitive core bash by default)
docker exec -it fuseki-app bash
# root@ffcd017e0b51:/jena-fuseki#
# inside the container fuseki-app
apt-get update;
# fix dependencies of apache-fuseki to use ps command line tool
apt-get install -y --no-install-recommends procps
# optionally add some tools you need
apt-get install -y --no-install-recommends vim nano tree # add some useful tools: editor vim, nano and listing with tree tool
apt-get install -y --no-install-recommends ruby-full # for data import with SPARQL over HTTP via ruby /jena-fuseki/bin/s-put and commands
# do your commands needed inside the container and eventually exit the docker container
exit |
Assuming #50 fixes this, can we close this issue? Or should we make a different issue to add |
This is probably the most relevant place to leave this for anyone else seeking answers since it's about the same error message: I also bumped into the database locking issue, but it was caused by |
@infinite-dao can you please update us if this if fixed for you now? |
+1 My config:
I login and create new database TS. And after run I see this Exception
|
The docker run --name fuseki-data_test20230112 --volume /fuseki busybox
# to create the data container
docker run --name fuseki-app_test20230112 --detach --publish 3030:3030 \
--env FUSEKI_DATASET_1=mydataset \
--env FUSEKI_DATASET_2=otherdataset \
--env ADMIN_PASSWORD="some-other-password" \
--env JVM_ARGS=-Xmx2g \
--volume /path/to/my/import/data:/import-data \
--volumes-from fuseki-data_20230112 \
stain/jena-fuseki:4.0.0 The fuseki interface did run, no log errors, but I expected that it should have created empty datasets, but there were none showing up in the fuseki interface, I could of course create some new using the interface, with no log errors. Restart the containers also no log errors. But in the end I did not dig deeper into where, any why, the empty datasets were not created. For me it works OK. |
What Fuseki Version are you running on? (Check e.g. like |
I still struggle with the README and the meant intention of “load” data into an existing container or afresh. After testing around, the point seems to me: the term “loading“ is describing it ambigous, it is not loading (in essence) meant to function (on running data sets), but only create from-data, i.e. only for the first time. Is that correct? Fuseki Server itself is meant to import data when the fuseki server itself is offline, because on a running fuseki server attempting to load data, it will not let you, and points you out that the database is locked ( So the question remains: How can one do that loading procedure the right way for an existing database? (e.g. using
|
Hi,
I found, that it does not create the dataset, the documentation is documenting, I guess it is not
FUSEKI_DATASET1
butFUSEKI_DATASET_1
… ;-) seeThe other thing I have a hard time to figure it out, is how to use volumes and to load data into that empty created database from before. I have no clue yet. I try to load just rdfs into
mydataset
.fuseki
and load data at the same time?fuseki-data
gets to know about the empty created database at start up, in which I want to load my data via command line.Thank you
The text was updated successfully, but these errors were encountered: