Bug #8827
synchronization doesn't update dateSystemMetadataModified if that's the only field that changed
0%
Description
It's been demonstrated that changing the dateSystemMetadataModified of an object's system metadata doesn't result in that change being synchronized with the CN unless there are other changes as well. Since in V2, the MN is authoritative for that field, the CN should perform a systemmetadata update command so it gets reflected on the CN.
Below is an example of what happens. Note that the object was picked up in the sync harvest, but then later ignored because nothing changed. Note that there are valid reasons to ignore updates with no changes, (resetting last harvest date), but this is not the same situation.
[ INFO] 2019-07-11 18:18:04,269 [ProcessDaemonTask2] (SyncObjectTask:executeTransferObjectTask:293) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 received [ INFO] 2019-07-11 18:18:04,270 [ProcessDaemonTask2] (SyncObjectTask:executeTransferObjectTask:310) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 submitted for execution [ INFO] 2019-07-11 18:18:04,270 [SynchronizeTask1251] (V2TransferObjectTask:call:209) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Locking task, attempt 1 [ INFO] 2019-07-11 18:18:04,365 [SynchronizeTask1251] (V2TransferObjectTask:call:214) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Processing SyncObject [ INFO] 2019-07-11 18:18:04,832 [SynchronizeTask1251] (V2TransferObjectTask:retrieveMNSystemMetadata:324) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Retrieved SystemMetadata Identifier:2650e74d-08d9-47d9-8478-d8ccc54ee9e from node urn:node:RW for ObjectInfo Identifier 2650e74d-08d9-47d9-8478-d8ccc54ee9e4 [ INFO] 2019-07-11 18:18:05,145 [SynchronizeTask1251] (V2TransferObjectTask:processUpdates:1107) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Start ProcessUpdate [ INFO] 2019-07-11 18:18:05,354 [SynchronizeTask1251] (V2TransferObjectTask:processV2AuthoritativeUpdate:1357) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - No changes to update. [ INFO] 2019-07-11 18:18:05,354 [SynchronizeTask1251] (V2TransferObjectTask:processUpdates:1139) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Completed ProcessUpdate [ INFO] 2019-07-11 18:18:05,453 [SynchronizeTask1251] (V2TransferObjectTask:call:241) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - Unlocked Pid. [ INFO] 2019-07-11 18:18:05,453 [SynchronizeTask1251] (V2TransferObjectTask:call:301) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 - exiting with callState: SUCCESS [ INFO] 2019-07-11 18:19:04,378 [ProcessDaemonTask2] (SyncObjectTask:reapFutures:372) Task-urn:node:RW-2650e74d-08d9-47d9-8478-d8ccc54ee9e4 SyncObjectState: SUCCESS
History
#1 Updated by Rob Nahf over 5 years ago
Look in class o.d.cn.batch.synchronization.type.SystemMetadataValidator.
There doesn't seem to be validators for filename and media type either.
