add validation and ignore out of order message when kind is updated
Users have reported issue with data duplication with following scenario:
- Trigger a re-index job for kinds: both raw and WKS kind at the same time
- The triggering of the reindexing on raw kind also triggered WKS service to recreate the WKS instances derived from them
- The target schema mapping for these raw records had been updated (e.g. version 1.0 to 1.1), meaning the new versions of these records created by WKS changed the schema.
- Index therefore received 2 events for the same WKS record instances at similar times, one to re-index the original and another to create the new one
- If the one to create the new instance for WKS was processed first that would lead to duplicates appearing.
This changes-set adds validation to avoid duplication by ignoring the event when kind is updated in such cases.
Merge request reports
Activity
added Azure Common Code GC IBM labels
added MRBugfix label
changed milestone to %M17 - Release 0.20
@Srinivasan_Narayanan Could you help check the azure deploy failure?
@Yauhen_Shaliou @Rustam_Lotsmanenko Any idea why the gc tests are failing ?
Sorry, infra issues, fixing them. cc: @Yurii_Ruban
Gc tests passed in the master branch. FYI: @Rustam_Lotsmanenko
@Rustam_Lotsmanenko @Yurii_Ruban can you please review the MR as well?
@Srinivasan_Narayanan Any luck with the azure deploy?
Hi @chad, team is looking into. @shivani_karipe , @nareshj update here plz.
Hi @chad, azure_deploy job is now successful.
https://community.opengroup.org/osdu/platform/system/indexer-service/-/jobs/1824459
mentioned in commit 0bdfd51f