Simplification of explore configuration
1. Whether explore is enabled is explicit property
2. All other explore properties derived from dataset properties if possible
Explore failure also fails the DTM operation that called it
Ability to communicate warnings to the user for successful explore operations
Enable/Disable explore as dataset management operations

Proposed Scope for 4.0

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
Simplify configuration of datasets
1. Schema and format as a system properties with validation
2. TTL as a system property
New API for a dataset type to declare what configuration it accepts (needed for Resource Center)
1. Properties (instance configuration)
2. Arguments (runtime configuration)
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
Simplify configuration of explore properties
1. Derived all explore properties from schema+format when possible.
2. Allow configuring the detailed explore properties (as today) for power users.
Improved control over transactions for programs
1. Configure transaction timeout as a runtime argument / preference at namespace, app, program level
2. Add APIs to Transactional that allow executing a transaction with custom timeout or without timeout

Versions Compared