...
Dependencies
Packages will only be able to specify dependencies on the CDAP version, as well as dependencies on the existence of specific CDAP entities. For example, the core-plugins-1.5.0 package requires that there exist system artifacts cdap-data-pipeline-4.0.0 and cdap-data-streams-4.0.0 in the CDAP instanceother packages.
| Code Block |
|---|
{
...
"dependencies": {
"cdap": {
"minVersion": "4.0.0",
"maxVersion": "4.1.0"
},
"artifactspackages": [
{
"scope": "system",
"name": "spark-plugins",
"minVersion": "1.5.0",
"maxVersion": "1.6.0"
},
...
],
"streams": [
{ "name": "smsTexts" }
],
"datasets": [
{ "name": "spamTexts" }
]
}
} |
...
}
} |
Min versions are inclusive and max versions are exclusive.
If other packages are listed as a dependency, the actions for the dependent package must be executed before the actions of the current package.
| Note |
|---|
Package dependencies introduces non-trivial logic in the UI and allow users to create some complex dependency chains. To simplify things in the first version, it may be a good idea to enforce that dependencies are only one level deep. That is, a package cannot depend on a package that has dependencies. |
Failures
Since a package spec can contain multiple actions, what happens if some actions succeed and then one action fails? Since the CDAP APIs backing these actions are idempotent, we can ask the user if they want to retry.
...