Story #8049
Support synchronization of system metadata for unhosted METADATA and RES_MAP objects
30%
Description
As part of mutable-content MN support, allow the MemberNode to keep the system metadata records for all resultant versions of its changeable entities. this allows them to keep accurate system metadata for every version even though they do not have the object bytes anymore for that version.
Benefits:
1. MN does not orphan any objects
2. MN can administer objects from past versions on their own MN. Adjust the access policy of all versions, for example.
3. don't need to call cn.setObsoletedBy or leave that field empty.
Costs:
1. requires new logic for indexing (possibly)
2. requires new logic for registerSystemMEtadata (possibly)
3. require new logic for synchronization
very similar to how we synchronize DATA objects, but don't trigger MN replication.
Associated revisions
refs #8049, provide clearer message when synchronization fails when a NotFound returned from MN.get()
refs #8049, provide clearer message when synchronization fails when a NotFound returned from MN.get()
History
#1 Updated by Dave Vieglais almost 7 years ago
- Sprint set to Infrastructure backlog
#2 Updated by Dave Vieglais almost 7 years ago
- % Done changed from 0 to 30
- Status changed from New to In Progress
