Staging instance, all changes can be removed at any time

Skip to content

Unify frontier definition between track-all vs track-first strategies

Previous definition for track-all was prone to inconsistencies in case the ingestion process crashes. Also, it was only meant to act differently for revisions that share content adn have the exact same timestamp (not a major improvement after all).

Depends on !113 (closed).


Migrated from D6746 (view on Phabricator)

Merge request reports

Loading