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 19
    • Merge requests 19
  • 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
  • #46
Closed
Open
Issue created Feb 09, 2021 by Alan Henson@alan.hensonDeveloper

Design consideration: Support transactions

One of the requirements made of ingestion is to support transactional capabilities while storing records. This would allow any process interacting with the Storage API to perform the following:

  • Begin a transaction
  • Modify one or more records (Create, Update, Delete, Purge) without any additional activity occurring (i.e., sending notifications)
  • Commit the transaction (persist all modifications in entirety with anyone error resulting in a rollback) - on success, release all notifications generated through the record modifications
  • Rollback the transaction (undo all modifications)

I'm sure there are other considerations involved with adding transactional support. These are some early thoughts to initiate the discussion.

The expectation is that this is feature is not considered until after Release 3.

Edited Feb 09, 2021 by Alan Henson
Assignee
Assign to
Time tracking