Manage Data Sources
Manage Data Sources allows the Data Engineer to register data sources to the system.
Actors
Extends Use Cases
Detail Scenarios
Scenario Deregister Data Source
Deregister Data Source allows the data engineer to remove a data source from the system. All BluePrints and DataFlows will no longer process data generated from the source. All data that has been registered to the Meta-data management system will be marked as unavailable, but the meta-data will continue to reside in the system.
Criteria
- Given - Data source 'myDataVolume1' is registered in the system using adaptor 'filesystem1'
- When - Data engineer uses 'datasource/list' method to deregister 'myDataVolume1'
- Then - Data source 'myDataVolume1' is registered in the system using adaptor 'filesystem1'
Steps
- dataadaptor create –name filesystem1 –file ./templates/dataadaptor-filesystem.yaml
- datasource create –name myDataVolume1 –adaptor filesystem1 –file ./templates/datasource.yaml
Actors
Scenario Register Data Source
Register Data Source to the system. This allows for data sources to be monitored. Data generated at the data source can now be processed by DataBluePrints.
Criteria
- Given - A system to monitor data sources
- When - A data source is registered to the system
- Then - A system to monitor data sources
Steps
- dataadaptor create –name filesystem1 –file ./templates/dataadaptor-filesystem.yaml
- datasource create –name myDataVolume1 –adaptor filesystem1 –file ./templates/datasource.yaml
- datasource create –name myDataVolume2 –adaptor filesystem1 –parameters host=localhost, filesystem=/tmp/user2
- datasource create –name myDataVolume3 –adaptor filesystem1 –parameters host=localhost, filesystem=/tmp/user3
- datasource create –name myDataVolume4 –adaptor filesystem1 –parameters host=localhost, filesystem=/tmp/user4