[Akonadi] Mechanism to re-try writing Item payload into backend
Open, Needs TriagePublic

Description

Historically (but even now, still) we had bugs that caused Item to not be written into the backend and lingering only in the database. This presents issues when using ItemRetriever, which will fail to update the Item in the DB with full payload, since the Item is marked as dirty (and likely lacks RID).

We should have a mechanism to force Akoandi to "flush" those pending changes into the backend again.

One idea is we could do this on start by checking for all dirty Items and sending out Append notifications to all resources.

dvratil created this task.Aug 6 2019, 10:03 AM