https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42508
--- Comment #41 from Tomás Cohen Arazi (tcohen) <[email protected]> --- Created attachment 199626 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199626&action=edit Bug 42508: Ensure ES deletion precedes DB deletion on patron removal Patron deletion must remove personal data from the ES index before removing it from the database. If the ES deletion fails (e.g., ES is unreachable), the entire operation is aborted to prevent personal data from being removed from the DB while remaining searchable in ES. This is relevant for GDPR-like compliance: a patron's right to erasure cannot be partially fulfilled. The full data lifecycle is covered: - Anonymize: patron.store() triggers ES reindex with scrambled data - Delete: ES deletion must succeed before DB deletion proceeds In batch scenarios (cleanup_database.pl), each patron deletion is independent. If ES is down, all deletions fail with a clear error, ensuring no data is removed from the DB without first being removed from all data stores. Test plan: 1. Apply patch 2. Enable ElasticsearchPatronSearch 3. Stop Elasticsearch 4. Attempt to delete a patron => FAIL: Deletion blocked with clear error message 5. Start Elasticsearch 6. Attempt to delete the same patron => SUCCESS: Patron removed from both ES and DB 7. Sign off :-D -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
