Change Details

This allows both the postgresql and cassandra backends to make efficient queries by using an index (resp. clustering key) instead of scanning all visits of the given origin then sorting by date. This does not affect the results for the last majority of cases, as ids are always in increasing chronological, unless an origin was re-loaded from an old archive.

This allows both the postgresql and cassandra backends to make efficient queries by using an index (resp. clustering key) instead of scanning all visits of the given origin then sorting by date. This does not affect the results for the last majority of cases, as ids are always in increasing chronological, unless an origin was re-loaded from an old archive. This should resolve [[ https://sentry.softwareheritage.org/organizations/swh/issues/9139/ | recurring timeouts ]] on this endpoint (6.4k occurrences in a month)

This allows both the postgresql and cassandra backends to make efficient queries by using an index (resp. clustering key) instead of scanning all visits of the given origin then sorting by date. This does not affect the results for the last majority of cases, as ids are always in increasing chronological, unless an origin was re-loaded from an old archive. This should resolve [[ https://sentry.softwareheritage.org/organizations/swh/issues/9139/ | recurring timeouts ]] on this endpoint (6.4k occurrences in a month)