Contents

...

•  User stories documented(Andreas)
•  User stories reviewed(Nitin)
•  User stories reviewed(Todd)
•  Requirements documented(Andreas)
•  Requirements Reviewed
•  Mockups Built
•  Design Built
•  Design Accepted

...

1. Minimal work to remove artifact management from DatasetTypeManager
   1. Remove the (experimental) REST API to deploy a dataset module by itself
   2. For dataset types/modules deployed from an app, remove the generation of an artifact. Instead record the app artifact that is was created from
   3. Similar as b. for dataset types included in plugins
   4. For apps, load dataset types from program class loader. For explore, load from the artifact recorded for the type
   5. May require some changes in artifact repository
2. Simplify configuration of datasets
   1. Schema and format as a system properties with validation
   2. TTL as a system property
3. New API for a dataset type to declare what configuration it accepts (needed for Resource Center)
   1. Properties (instance configuration)
   2. Arguments (runtime configuration)
4. Make dataset lifecycle methods (create, update, drop) consistent
   1. In case of failure, do not leave partial/inconsistent state behind
   2. Do not silently ignore explore failures: they must fail the entire operation
5. Simplify configuration of explore properties properties CDAP-2790 
   1. Derived all explore properties from schema+format when possible. 
   2. Allow configuring the detailed explore properties (as today) for power users.
6. Improved control over transactions for programs CDAP-7319
   1. Configure transaction timeout as a runtime argument / preference at namespace, app, program level CDAP-6103
   2. Programmatic APIs for programs that allow executing a transaction with custom timeout CDAP-7193, CDAP-7320, CDAP-7322
   3. Add a way to access datasets (and call non-transactional methods) CDAP-7323

...