...
- Stabilization of existing dataset framework:
- improve performance and throughput
- better error handling - atomicity of dataset admin
- reduce footprint on transaction system
- Definition of new dataset APIs
- Dataset capability interfaces: @Read, @Write, @ReadWrite
- Dataset admin APIs: "Updatable"
- create in configure() if dataset exists is an update
- update with compatibility check
- distinguish update from upgrade
- Implementation new APIs for existing system datasets:
- Table, FileSet
- Schema as a system property
- Transactions:
- customizeable transaction timeout in programs
- long transactions in programs
- dataset access without transaction
- read-only transactions
- Major Bugs
- fix in-Memory table
- remove buffering in MR/Spark
- Management
- create in configure() if dataset exists is an update
- update with compatibility check distinguish update from upgrade
- dataset types should have aliases, register only once