Project

General

Profile

Bug #4182

sync is generating syncFailed on "empty updates"

Added by Rob Nahf about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Robert Waltz
Category:
d1_synchronization
Target version:
Start date:
2013-11-21
Due date:
2013-11-23
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

In STAGE, objects reharvested generate syncFailed exceptions when there are no changes.

The reharvest treats the task as an update to the systemMetadata, and when it doesn't find a change in the two fields that are allowed to change, it assumes there is a change somewhere else, which would be disallowed, so generates a syncFailed. If nothing has changed, a syncFailed is still thrown.

Also, by visual inspection, the TransferObjectTask.updateSystemMetadata logic is inadequate in that it only updates either the obsoletedBy or the isArchived field, but not both, which seems to be possible with non-API changes to systemMetadata.

History

#1 Updated by Rob Nahf about 8 years ago

  • Description updated (diff)

#2 Updated by Rob Nahf about 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

fixed TransferObjectTask.updatesystemMetadata logic to address both cases. (when both setObsoletedBy and archived have changed, and throwing an exception when objects are reharvested - it now checks that the dataSystemMetadataModified date is later than what the cn's have.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)