Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-1032

UUID Type 1 timestamp-based Path ID Mapper

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Fedora 3.5
    • Fix Version/s: None
    • Labels:
      None
    • Roadmap Theme:
      Scalability/Performance

      Description

      Given a Type 1 UUID pid, e.g. demo:8e25cab0-167d-11e1-be50-0800200c9a66, I would like to have the object stored on the filesystem based on the uuid-encoded timestamp, e.g.
      $FEDORA_HOME/data/objectStore/2011/11/24/info%3Afedora%2Fdemo%3A8e25cab0-167d-11e1-be50-0800200c9a66.

      The timestamp-based path mapping should be configurable, e.g. yyyy/MM/dd, and yyyy/MM/dd is a reasonable default. The Path ID Mapper must be able to accommodate non-type1 UUID identifiers as well, falling back to the default, hash-based algorithm.

      Rationale: We mint UUIDs for >95% of our repository objects. It's also the case that it's only the most recently ingested/modified objects that are most frequently accessed. Given the scale of our repository, we'd like to be able to make storage policy decisions (slow/fast storage, backup policies) based on the age (i.e. importance) of the object. This also allows us to prioritize the restore of objects in a disaster recovery scenario.

        Attachments

          Activity

            People

            Assignee:
            eddie Edwin Shin
            Reporter:
            carlo.reiffers Carlo Reiffers
            Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: