CN synchronization should handle system metadata with existing obsoletes/obsoletedBy fields
When the CN tries to sync an object from mn-stage-ucsb-1 (with existing KNB data), objects with system metadata that includes obsoletes/obsoletedBy fields throws:
here's the error:
[ERROR] 2012-03-19 14:37:46,387 (TransferObjectTask:write:389) Task-urn:node:mnStageUCSB1-knb-lter-hfr.108.12
<?xml version="1.0" encoding="UTF-8"?>
The supplied system metadata is invalid. The obsoletes field cannot have a value when creating entries.
The system metadata reflects the current state of the revisions (and I think Ben has been iterating through revisions in order to generate the initial system metadata document.)
The CN should probably be more lax about existing obsoletes/obsoletedBy fields since the the MN knows the revision history and can generate the system metadata appropriately. Otherwise, the intitial revision would have to be sync'd, and then updates to it would have to occur to get to the most recent revision. We probably don't need to go through this artificial sequence.
#1 Updated by Chris Jones about 11 years ago
- Category changed from d1_synchronization to Metacat
- Assignee changed from Robert Waltz to Chris Jones
Reassigning - Robert pointed out this was coming from Metacat
#2 Updated by Chris Jones about 11 years ago
- Status changed from New to Closed
I've modified MNodeService and D1NodeService to only perform the obsoletes/obsoletedBy check on the MN side.