Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Target releaseJeff Nelson
Epic CON-33 - Getting issue details... STATUS
Document statusDRAFT
Document owner

Jeff Nelson

Designer
DevelopersJeff Nelson
QA

Goals

  • Add the ability to import data from a file, stream, etc into Concourse

Background and strategic fit

We need to give users the ability to bulk import data into Concourse. This data may be in different formats (i.e. SQL, CSV, etc) in various formats (i.e. file, url, stream, etc). This feature will enable more testing because it will be easier to seed Concourse with large and diverse data sets. This feature will also lead to increased Concourse usage by third party applications because they will be able to take data from their existing stores and bring it into Concourse.

Assumptions

  • This feature will be used to seed testing environments
  • This feature will be used by technical end-users to initially seed their staging Concourse deployment for testing and comparison with legacy databases.
  • This feature will be used by technical end-users to initially seed their production Concourse deployment.
  • The typical end-user is technically competent and has access to the command line
  • Data sets will come in various formats, including SQL, CSV, Excel, etc
  • Data sets will come in various forms, including file, url, stream, etc

Requirements

#TitleUser StoryImportanceNotes
1Abstract boilerplate logic
     

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • No labels