Bug #3106
Synchronization may miss updated entries during harvesting
Status:
Closed
Priority:
Normal
Assignee:
Robert Waltz
Category:
d1_synchronization
Target version:
Start date:
2012-07-30
Due date:
% Done:
100%
Milestone:
CCI-1.0.4
Product Version:
*
Story Points:
Sprint:
Description
If synchronization is processing the harvested list from a MN, and the MN updates a record that is part of the harvested list, then the lastModifiedDate of the update will be reflected in the DateLastHarvested field of the node.
This may cause any concurrent updates of records that had previously been synchronized during the current run, to be missed in a subsequent run.
History
#1 Updated by Robert Waltz over 12 years ago
- Target version changed from Sprint-2012.29-Block.4.3 to Sprint-2012.33-Block.5.1
#2 Updated by Robert Waltz about 12 years ago
- Target version changed from Sprint-2012.33-Block.5.1 to Sprint-2012.35-Block.5.2
#3 Updated by Rob Nahf about 12 years ago
Ah, nice one. I guess if you put a toDate in the sync query, then reject any updates if their modification date is later than the toDate, you can keep the dateLastHarvested honest?
#4 Updated by Robert Waltz about 12 years ago
- Status changed from In Progress to Testing
#5 Updated by Robert Waltz about 12 years ago
- Status changed from Testing to Closed
