You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
This page documents the incompatible changes between CDAP 4 and CDAP 5.
| Change | Impact | CDAP 5 Behavior |
|---|
No centralized management of dataset modules, types, jars | - Cannot use dataset classes that are not included in the same application artifact
- Explore service won't able to instantiate dataset instance for
RecordScannable / RecordWritable implementations- Only affect
Table based dataset, not affecting FileSet based dataset
| - Dataset classes should always be inside the application artifact jar
|
| Default tx control for program will be explicit (except Flow) | - Transactional operations need to be wrapped with
Transactional.execute
| - In cloud runtime, calling
Transactional.execute will result in exception
|