Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Storage
  • Issues
  • #42
Closed
Open
Issue created Dec 14, 2020 by Gary Murphy@gtmurphyDeveloper

[Storage] Removal of Requirement that Data Partition ID is the first component of the Kind property

As part of integrating with the new Schema Service (see indexer-service#7 (closed)), it was realized that a change of behavior is needed in the Storage service treatment of the "kind" property. Previously, it was required that data-partition-id was the first component of the "kind" property (i.e. data-partition-id:source:entitytype:version). However, with the Schema Service, there can be cross-partition schema authorities that should not be the data-partition-id.

An example of this would be "OSDU:wks:wellbore:". Here, "OSDU" is not a data-partition-id, but an authority that spans data partition concerns. To use this Schema scoping paradigm, Storage service needs to relax the check so that kind first component != data-partition-id destination for the storage record.

Assignee
Assign to
Time tracking