Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • F File
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • 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
  • File
  • Issues
  • #7
Closed
Open
Issue created Aug 19, 2020 by Dania Kodeih (Microsoft)@dkodeihReporter

Refactor File Service

The file service was initially designed with a basic workflow in mind and didn't cover all the potential use cases that would benefit from having a dedicated file interface to the provider platform. In order to expand the file service features, we propose having a design session with a better alignment with its intended use and supporting more scalable scenarios:

Here are a few suggestion:

  1. decouple the getLocation from the put file operations
  2. distinguish landing zone operations from file operations
  3. rename API calls to be more functionally significant
  4. add a put file operation so that applications can iterate or parallelize
  5. support no-database implementation for providers that can retrieve meta-data from the Blob (ex, POSIX-like)
  6. support POSIX interop (to be discussed)
  7. add a create "container" operation to allow the following flow
  • create container, returns SAS token
  • iterate through a number of files, upload files (upload can be done in place);
  • close container, return file list

==================

  • File service should have functionality to access file by FileID (FileID -> SignedURL)
Edited Aug 27, 2020 by Dmitriy Rudko
Assignee
Assign to
Time tracking