Improve out-of-order revision processing
Fix issue when processing revision in batch
If any revision in the batch was invalidating a frontier, the commit of the complete batch failed. This is now fixed.
Refine maxdate calculation
Improve out-of-order revision processing
Added a flag to the IsochroneNode
to identify invalidated frontiers
and force its update later when processing the graph. This should
guarantee the same results when processing revision one-by-one vs. in
batches (in terms of db rows).
Remove directory_invalidate_in_isochrone_frontier
method from provenance interface
It was meant to be used in a multi-thread scenario which is not possible
due to Python's lack of actual parallelism. This way the
build_isochrone_graph
function is guaranteed not to modify the DB (it
performs only reads now). Also the isochrone graph test was updated to
use revision_add
with a new flag to avoid commits, hence emulating the
batch processing behaviour.
Depends on !34 (closed)
Migrated from D5847 (view on Phabricator)