Story #7196
Refactor DataPackage to support both v1 and v2 system metadata
Status:
Closed
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
d1_libclient_java
Target version:
Start date:
2015-06-16
Due date:
% Done:
100%
Story Points:
Sprint:
Description
DataPackage needs to be refactored to use both V1 and V2 Sysmeta, handle mixed MNs
History
#1 Updated by Dave Vieglais over 9 years ago
- Target version changed from CCI-2.0-TRUNK to CCI-2.0.0
#2 Updated by Dave Vieglais over 9 years ago
- Category set to d1_libclient_java
#3 Updated by Ben Leinfelder over 9 years ago
- Assignee changed from Chris Jones to Ben Leinfelder
- Status changed from New to In Progress
- % Done changed from 0 to 30
#4 Updated by Ben Leinfelder over 9 years ago
- Status changed from In Progress to Closed
- % Done changed from 30 to 100
There's now a corresponding DataPackage "convenience" class for supporting V2 types and APIs. In a mixed MN scenario, the D1Object does it's best to download an appropriate object from the ObjectLocationList it gets from the CN. As long as there is one replica of the object on a MN that supports the version of Datapackage being used, the package will be constructed as expected. If that is not the case (e.g., the object only lives on v1 MNs and we are using a v2.Datapackage) then the user will need to use a v1.Datapackage instead.
#5 Updated by Rob Nahf over 9 years ago
- Target version changed from CCI-2.0.0 to CLJ-2.0.0
moving to CLJ so it's not forgotten come release notes time.
