Bug #5176
closedConfiguration to disable writing/updating/deleting function on metacat, but allow reading/querying
0%
Description
This scenario happened couple times:
An administrator tried to use a new machine to replace the old one. Eventually the new one will use the DNS name of the old one and will have all documents/data from the old one.
The administrator always dumps the old db to a file and run this file on the new machine. For a big metacat server, the transformation may take a while. So administrator want users still can read/query documents/data from the old hardware, but they can't write/update documents/data to the old one. This can make sure that the old metacat and new metacat have the identical documents/data.
We may add a new property on the metacat.properies file, see disableWriting. Its default value is false. When the property is set to be true, users can read/query documents, but can't write/update/delete documents (include replication).
Updated by Matt Jones almost 14 years ago
The problem with this is that Metacat keeps an access log that records read operations as well as the others. So even doing a read changes the database. The only effective way to prevent changes to the database is to shut down the instance I think.
Updated by Jing Tao almost 14 years ago
Yeah, reading can changes the database. So maybe shutting down the instance is the only choice.
Updated by ben leinfelder over 11 years ago
We can't really do this since we need to log all activity even if it is read-only activity.