Skip to content

Intrinsic identifiers for origins

We currently use an incrementing integer to uniquely identify origins. This does not work well with a distributed database (eg. Cassandra), and is not an intrinsic identifier like most of the archive.

So we should define a new identifier for origins. Current options:

  1. A 2-tuple: (type, url). Pros: useful information can be derived that identifier without an API request.
  2. A hash of the type and url. Pros: fixed-size and compact

Migrated from T1731 (view on Phabricator)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information