Hi olivier,
No reason I can think of except being clear that updates to the file
will not be written back to the file.
Given the user has explicitly given "--update", allowing update seems
quite reasonable.
Recorded:
https://github.com/apache/jena/issues/1228
(we now have github issues enabled for the codebase - use JIRA or GH issues)
Andy
On 21/03/2022 02:41, Olivier Dameron wrote:
Hello,
When I run
${FUSEKI_HOME}/fuseki-server --file=someFile.ttl --update /dataset
the log displays:
INFO Server :: Dataset: in-memory: load file: someFile.ttl
INFO Server :: Running in read-only mode for /dataset
...
and indeed, update queries are not possible in spite of the --update
option:
INFO Fuseki :: [3] POST http://localhost:3030/dataset/update
INFO Fuseki :: [3] No Fuseki dispatch /dataset/update
Is it the normal behavior?
The --help option displays
--mem Create an in-memory, non-persistent dataset for the server
--file=FILE Create an in-memory, non-persistent dataset for the server,
initialised with the contents of the file
--update Allow updates (via SPARQL Update and SPARQL HTTP Update)
So I do not see any indication that --file should be read-only
Note that I managed to get the update working by
1. running the server with an empty dataset
${FUSEKI_HOME}/fuseki-server --mem --update /dataset
yes - not much point having a read-only empty dataset.
2. manually uploading someFile.ttl via the GUI
but doing things manually is cumbersome :-)
Thank you
olivier
