-
- Downloads
origin layer: retrieve multiple levels of revision history at once
Replace `revision_get_parents` with `revision_get_some_outbound_edges`, which can optionally retrieve more levels of history than just a single one. This allows us to do way fewer queries on the swh.graph or swh.storage backend if the revision exists there. The swh.storage backend does limited recursion, so we still process the origin in multiple steps to fetch the whole history.
Showing
- swh/provenance/archive.py 9 additions, 6 deletionsswh/provenance/archive.py
- swh/provenance/graph.py 21 additions, 22 deletionsswh/provenance/graph.py
- swh/provenance/interface.py 4 additions, 6 deletionsswh/provenance/interface.py
- swh/provenance/journal_client.py 0 additions, 1 deletionswh/provenance/journal_client.py
- swh/provenance/model.py 1 addition, 19 deletionsswh/provenance/model.py
- swh/provenance/multiplexer/archive.py 17 additions, 11 deletionsswh/provenance/multiplexer/archive.py
- swh/provenance/origin.py 10 additions, 16 deletionsswh/provenance/origin.py
- swh/provenance/postgresql/archive.py 16 additions, 11 deletionsswh/provenance/postgresql/archive.py
- swh/provenance/provenance.py 13 additions, 15 deletionsswh/provenance/provenance.py
- swh/provenance/storage/archive.py 8 additions, 4 deletionsswh/provenance/storage/archive.py
- swh/provenance/swhgraph/archive.py 14 additions, 9 deletionsswh/provenance/swhgraph/archive.py
- swh/provenance/tests/test_archive_interface.py 17 additions, 12 deletionsswh/provenance/tests/test_archive_interface.py
Loading
Please register or sign in to comment