Project

General

Profile

Bug #6576

Ensure replicaPolicy node list order is preserved in backing store

Added by ben leinfelder about 6 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

This came up during the D1 tidy process and it turns out that Metacat does not have any mechanism to ensure the preferred/blocked list order is preserved when it stores/retrieves from the postgres table. The XML and java structures are ordered and we should make sure to respect and preserve that order.
https://redmine.dataone.org/issues/4214

History

#1 Updated by ben leinfelder about 6 years ago

  • Assignee set to ben leinfelder
  • Description updated (diff)

#2 Updated by ben leinfelder almost 5 years ago

  • Target version changed from 2.5.0 to 2.5.1

Looking at the DataONE ticket for this, there doesn't seem to be a conclusion. The main issue being for the tidy process and not for correct day-to-day working of d1-replication. Deferring in Metacat.

#3 Updated by Jing Tao almost 5 years ago

  • Assignee changed from ben leinfelder to Jing Tao

#4 Updated by ben leinfelder almost 5 years ago

  • Target version changed from 2.5.1 to 2.6.0

#5 Updated by Jing Tao over 4 years ago

  • Status changed from New to Closed

A new column policy_id was added to the smReplicationPolicy table. When we get data from the table, the mn list will be ordered by this column.

Also available in: Atom PDF