search

MI-DPLA / combine

Combine /kämˌbīn/ - Metadata Aggregator Platform
MIT License
26 stars 11 forks source link

Record can end up with nonexistent Job id #427

Open antmoth opened 5 years ago

antmoth commented 5 years ago

I have a situation where three of my records have a job_id that doesn't exist, and no idea how they got that way:

> db.record.find( { job_id : 7 } ).count()
3
> db.record.find( { job_id : 8 } ).count()
0
> db.record.find( { job_id : 6 } ).count()
657
> db.record.find( { job_id : 5 } ).count()
995
> db.record.find( { job_id : 4 } ).count()
993
> db.record.find( { job_id : 3 } ).count()
2976
> db.record.find( { job_id : 2 } ).count()
969
> db.record.find( { job_id : 1 } ).count()
3644
> db.record.find( { job_id : 0 } ).count()
0
antmoth commented 4 years ago

Pretty sure this is caused by deleting a Job from MySQL, which does not sync with mongo