...
| Code Block |
|---|
public interface ApplicationContext<T extends Config> {
T getConfig();
}
public interface Application<T extends Config> {
void configure(ApplicationConfigurer configurer, ApplicationContext<T> context);
}
public abstract class AbstractApplication<T> implements Application<T extends Config> {
...
protected final ApplicationContext<T> getContext() { return context; }
}
public class MyApp extends AbstractApplication<MyApp.MyConfig> {
public static class MyConfig extends Config {
@Nullable
private String stream;
@Nullable
private String table;
private MyFlowConfig flowOptions;
private MyConfig() {
this.stream = "A";
this.table = "X";
}
}
public void configure() {
// ApplicationContext now has a method to get a custom config object whose fields will
// be injected using the values given in the RESTful API
MyConfig config = getContext().getConfig();
addStream(new Stream(config.stream));
createDataset(config.table, Table.class);
addFlow(new MyFlow(config.stream, config.table, config.flowOptions));
}
} |
Story Details
...
Deploying an Application
Users will still be able to deploy an app in one call. Suppose a user wants to deploy their application contained in myapp-1.0.0.jar. They make the same RESTful call they would today:
...
| Code Block |
|---|
PUT /namespaces/default/apps/myapp2 -H "Content-Type: application/json" -d '{ "artifact": { "name": "myapp", "version": "1.0.0" }, "config": { "stream": "B", "table": "X" } }' |
Deploying an Artifact, then an Application
Users can also deploy an artifact without creating an application.
...
| Code Block |
|---|
PUT /namespaces/default/apps/myapp3 -H "Content-Type: application/json" -d '{ "artifact": { "name": "my-app", "version": "1.0.1" }, "config": {"stream": "C", "table": "X"} }' |
Updating an Application
Users will also be able to update their applications to use a different version of an artifact.
| Code Block |
|---|
PUT /namespaces/default/apps/myapp/properties -H "Content-Type: application/json" -d '{ "artifact": { "name":"myapp", "version":"1.0.1" }, "config": { "stream": "A", "table": "X" } }' |
System Artifacts
System artifacts are special artifacts that can be accessed in other namespaces. They cannot be deployed through the RESTful API. Instead, they are placed in a directory on the CDAP master host. When CDAP starts up, the directory will be scanned and those artifacts will be added to the system. Example uses for system artifacts are the ETLBatch and ETLRealtime applications that we want to include out of the box. When a user wants to create an application from a system artifact, they make the same RESTful call as before, except adding the namespace to the artifact section of the call:
| Code Block |
|---|
PUT /namespaces/default/apps/somePipeline -H "Content-Type: application/json" -d '{ "artifact": { "namespace": "system", "name":"ETLBatch", "version":"3.1.0" }, "config": { ... } }' |
RESTful API changes
Application APIs
...