[
https://issues.apache.org/jira/browse/JENA-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213991#comment-13213991
]
Andy Seaborne commented on JENA-214:
------------------------------------
This needs to "work nice" with the configuration file as that's the way
everything should be done.
To create a permanently read-only datasets, you configure in only read-only
services.
Either this feature must know which services are write so as to set some flag
as it's one servlet instance per service per dataset or the config needs
modifying carefully.
Maybe instantiate a wrapper service that has the old service, and is read-only,
then when the reverse is done, get only service and put back in place.
Or a wrapper for the dataset and change the dataset acted on.
The wrapper is only present while in a temporary read-only mode not permanently
there although that could be done as well. Seems heavy weight for this special
feature.
> Allow to set Fuseki (or a single dataset) in read-only mode (and eventually,
> back into read-write mode)
> -------------------------------------------------------------------------------------------------------
>
> Key: JENA-214
> URL: https://issues.apache.org/jira/browse/JENA-214
> Project: Apache Jena
> Issue Type: New Feature
> Components: Fuseki
> Reporter: Paolo Castagna
> Priority: Minor
> Attachments: ActionReadOnly.java
>
>
> A very useful MgtCmdServlet with commands such as: "backup", "shutdown", etc.
> is now available in Fuseki.
> This is proposing a new command to set the server (or a single dataset) in
> read-only mode and back into read-write mode.
> A use case for this would be to perform a replication via rsync, in order to
> replicate TDB indexes from server A to server B both servers needs to be set
> to read-only mode first, the replication can start, when it finishes both
> servers can be configured back to read-write mode.
> Another use case would be, enabling a backup with an external tool or any
> other operation which needs to have exclusive access to TDB indexes and/or
> ensure all data has been flushed to disk and there are no in-flight write
> transactions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
