This is to detect non-durable job suddenly disappearing when concurrently completing. On MariaDB/MySQL the fall-through code path select-update-insert can be taken due to consistent nonblocking read and multi-version concurrency control.
This PR...
Fixes issue #1085
Changes
The code change checks the update count returned when storing a job.
Checklist
[x] tested locally
[x] updated the docs (not applicable, bug fix only)
[x] added appropriate test (not applicable, storeJob method covered in tests already)
[x] signed-off on the DCO referenced in the CONTRIBUTING link below via git commit -s on my commits, and submit this code under terms of the Apache 2.0 license and assign copyright to the Quartz project owners
This is to detect non-durable job suddenly disappearing when concurrently completing. On MariaDB/MySQL the fall-through code path select-update-insert can be taken due to consistent nonblocking read and multi-version concurrency control.
This PR...
Fixes issue #1085
Changes
The code change checks the update count returned when storing a job.
Checklist
git commit -s
on my commits, and submit this code under terms of the Apache 2.0 license and assign copyright to the Quartz project ownersIn submitting this contribution, I agree to the terms of contributing as referred to here: https://github.com/quartz-scheduler/contributing/blob/main/CONTRIBUTING.md