Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • S sysadm-environment
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 181
    • Issues 181
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Platform
  • Infrastructure
  • sysadm-environment
  • Issues
  • #2343
Closed
Open
Issue created Mar 31, 2020 by vlorentz@vlorentzMaintainer

Decide where/how to store extrinsinc metadata

Before implementing the metadata spec, we need to know where to implement it in; so we need to decide where to store it.

I see three options:

  1. in the main swh-storage, which may cause some issues scaling
  2. implemented in swh-storage, but running on a different postgres/cassandra cluster, which might be confusing
  3. implemented in a new component entirely, which adds some complexity and code duplication with swh-storage if we decide to use postgres or cassandra

Migrated from T2343 (view on Phabricator)

Edited Oct 18, 2022 by vlorentz
Assignee
Assign to
Time tracking