Task #3062
Updated by Robert Waltz about 11 years ago
remove line 569 in TransferObjectTask
Does the CN have the right to assign Authoritative member node. Ben says no. The other membernode may be authoritative.
Updates to obsoletedBy and archive flags may only be from authoritative membernodes.
I want to revert changes to TransferObjectTask
Need to discuss what Matt has to say about client-MN interactions of Morpho. someone may have update capability on an object but not have permission to modify on the authoritative MN.
authoritativeMN must be set by the MemberNode- LTER may have replica information for other MNs that may be synchronized first.
if the authoritative memberNode is not originMember node, then it is considered a replica.
Replica's may not be created before the original Object is synchronized from the Authoritative membernode. CN V1 does not have a way to update systemMetadata, so if jthe replica is created, then any systemMetadata information contained in the replica will be definitive for the original object. (e.g. OriginMember node will always be listed as the replica membernode and not the true origin of the object).
Does the CN have the right to assign Authoritative member node. Ben says no. The other membernode may be authoritative.
Updates to obsoletedBy and archive flags may only be from authoritative membernodes.
I want to revert changes to TransferObjectTask
Need to discuss what Matt has to say about client-MN interactions of Morpho. someone may have update capability on an object but not have permission to modify on the authoritative MN.
authoritativeMN must be set by the MemberNode- LTER may have replica information for other MNs that may be synchronized first.
if the authoritative memberNode is not originMember node, then it is considered a replica.
Replica's may not be created before the original Object is synchronized from the Authoritative membernode. CN V1 does not have a way to update systemMetadata, so if jthe replica is created, then any systemMetadata information contained in the replica will be definitive for the original object. (e.g. OriginMember node will always be listed as the replica membernode and not the true origin of the object).
