Open Bug 1421464 Opened 5 years ago Updated 19 days ago
Advance history engine's last
Sync timestamp as we add visits to places
In bug 1416788 we decided to "chunk" the calls made to places to insert history as specifying too many visits in one call has bad consequences. We should upgrade that so it (a) sorts the records by the last modified timestamp, and (b) advances the lastSync timestamp of the engine as we go. This will mean that if sync is interrupted it has more chance of not reapplying those same records each time.
Currently, updating lastSync requires us fetch all the items we need to backfill. Failing to do this would mean we never backfill these items. This is costly, but the best/only plan we have to reduce the cost of it is bug 1435007, so I don't think we should do this without that one (nor can we, really). In the mean time we have a P3 blocking a P2 which seems wrong... but oh well.
Depends on: 1435007
This is P3 since we have a P3 blocking it.
Priority: P2 → P3
Assignee: nobody → chiovolonit
You need to log in before you can comment on or make changes to this bug.