Story #8173
add checks for retrograde systemMetadata changes
Start date:
2017-09-01
Due date:
% Done:
0%
Story Points:
Sprint:
Description
with the ability to prioritize and the introduction of parallelized index task processing, the effective queue is not guaranteed to be time-ordered. If there are two valid system metadata changes resulting in two tasks and the second change hits the index first, the earlier task should be rejected, as its changes are out of date.
Related issues
History
#1 Updated by Rob Nahf about 7 years ago
- Related to Task #7771: Use multiple threads to index objects added
#2 Updated by Dave Vieglais about 7 years ago
- Target version changed from CCI-2.3.5 to CCI-2.3.6
#3 Updated by Jing Tao about 7 years ago
- Target version changed from CCI-2.3.6 to CCI-2.3.7
#4 Updated by Dave Vieglais about 7 years ago
- Assignee changed from Rob Nahf to Jing Tao
#5 Updated by Jing Tao about 7 years ago
- Target version changed from CCI-2.3.7 to CCI-2.4.0
Our new hazelcast event filter has the function. But after we transfer to RabbitMQ mechanism, we will need another one. So i move it to 2.4.
#6 Updated by Dave Vieglais almost 7 years ago
- Sprint set to Infrastructure backlog
