- How to upload an Artifact:
In order to create applications with versions, the artifact jars (which contains CDAP application) needs to be uploaded first. Once an artifact is uploaded, an application can be created from it by optionally providing a configuration.
POST /v3/namespaces/<namespace-id>/artifacts/<artifact-id> --data-binary @path/to/file-1.1.0.jar
You can view the information about artifacts deployed using the GET /v3/namespaces/<namespace-id>/artifacts endpoint.
- How to Create multiple versions of an Application:
POST /v3/namespaces/<namespace-id>/apps/<app-id>/versions/<version-id>/create
Body: { "artifact": { "name": "WordCount", "version": "3.5.1", "scope": "user"}, "config": {"stream": "purchaseStream"} }
...
Deterministic routing - call methods of a service of a specific version (service of that version should be running)
METHOD /v3/namespaces/<namespace-id>/apps/<app-id>/versions/<version-id>/services/<service-id>/methods/<method-name>
Note: Deterministic routing through version-id in the REST API works only in SDK. In distributed mode, as a workaround, the routeconfig can be used to set 100% routing to a version that is desired. This will be fixed in 3.6 (CDAP-7331).
Configuration based Routing – configuration based routing will be used when the method call is made to non-versioned API:
METHOD /v3/namespaces/<namespace-id>/apps/<app-id>/services/<service-id>/methods/<method-name>
Say, if the configuration is : { "v1" : 30, "v2" : 30, "v3" : 40 } : 30% of requests are routed to version v1, 30% requests are routed to version v2, 40% requests are routed to v3
...