Task #7254
v2 MN.create() followed by v1 MN.update() on same node shouldn't overwrite SID
0%
Description
After using an MN's v2 endpoint to create a v2 object,
using update() on the v1 endpoint on that node,
the system metadata for that object should still have the same SID as the previous version's sysmeta.
The v1 update() will contain sysmeta without a SID, but since we're updating a v2 object, we don't want to lose the SID assigned at v2 create() time.
We want the sysmeta created for the new object to keep the SID from the previous (v2) sysmeta.
Corresponding test: V1V2InteropFunctionalIT.testV2CreateV1UpdateSameNode()
History
#1 Updated by Jing Tao over 9 years ago
- Target version set to CCI-2.0.0
#2 Updated by Jing Tao over 9 years ago
- Status changed from New to Rejected
- translation missing: en.field_remaining_hours set to 0.0
A SID chain can be terminated by a new version of object with SID=null in the system metadata. If we want v1.update always keep the existing sid of the previous version object, we can't use this v1.update method to terminate the sid chain (purposely to update the object with sid=null).
And, there is no reason to call a v1.update method on an object with v2 system metadata.
