Skip to content

Require a follow-up issue for synch index creation/deletion

Abdul Wadood requested to merge abdwdd-sync-database-add-guidelines into master

What does this MR do and why?

After creating the async indexes, I missed creating their sync counterparts which I later created in !108973 (merged) after some milestones passed.

To not miss the creation/deletion of sync counterparts of the async indexes, there should be a follow-up issue created by the author to create/destroy the sync indexes. I have added an issue template for it and have set its due date in 2 weeks as the index should ideally get created in a week.

Another way to strictly enforce this is to change the prepare_async_index (and prepare_async_index_removal) method signature to require a follow-up issue link parameter but it would pollute our codebase with issue links.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Abdul Wadood

Merge request reports