Project

General

Profile

Task #3745

Story #3729: Member Nodes should be the authoritative source of System Metadata

Add Replica version attribute

Added by Chris Jones over 11 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
2013-05-07
Due date:
% Done:

0%

Estimated time:
80.00 h
Milestone:
None
Product Version:
Story Points:
Sprint:

Description

We currently use SystemMetadata.serialVersion to manage versions of system metadata with the list of replicas. This needs to be separated out, so the CNs can manage the Replica list independently of the SystemMetadata. Change the dataoneTypes.xsd schema to add an optional 'version' attribute to the Replica object. This will be backwards-compatible with previous system metadata instances, and will allow us to manage each replica's status individually.

...
/d1:replica

Add API calls for:

CNReplication.setReplicaVersion()
CNReplication.getReplicaVersion()

This change will affect the following components:
d1_schema
d1_common_java
d1_common_python
d1_libclient_java
d1_libclient_python
d1_cn_rest
d1_cn_rest_proxy
Metacat CNodeService

History

#1 Updated by Robert Waltz about 10 years ago

  • Target version set to CCI-2.0.0

#2 Updated by Rob Nahf over 9 years ago

  • Status changed from New to Rejected
  • translation missing: en.field_remaining_hours changed from 80.0 to 0.0

we determined that serial version could still be be used for tracking replica status updates under v2 (the CN is still authoritative on that property)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)