Project

General

Profile

Bug #5176

Configuration to disable writing/updating/deleting function on metacat, but allow reading/querying

Added by Jing Tao about 10 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
09/15/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5176

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).

History

#1 Updated by Matt Jones about 10 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.

#2 Updated by Jing Tao about 10 years ago

Yeah, reading can changes the database. So maybe shutting down the instance is the only choice.

#3 Updated by ben leinfelder over 7 years ago

We can't really do this since we need to log all activity even if it is read-only activity.

#4 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 5176

Also available in: Atom PDF