1.2.0-SNAPSHOT (ElAlto - under development)
WARNING
This is a work in progress. Do not use unless you know what you are doing!
1.1.4
- Config Binding Service client
- predefined parsers for input and output streams
- remove the need for a DCAE application to manually interpret streams_publishes (
Sink
s) and streams_subscribes (Source
s) parts of the configuration - available parsers for DMaaP Message Router and DMaaP Data Router streams
- experimental support for Kafka streams
- remove the need for a DCAE application to manually interpret streams_publishes (
- support for other CBS endpoints besides get-configuration: get-by-key, get-all (introduces minor but breaking changes)
- predefined parsers for input and output streams
- DMaaP client
- New, experimental DMaaP client. It's not ready for use yet (not integration tested with DMaaP instance). However, you can use this API if you target El Alto release (note that some minor interface changes might be introduced).
- Internals:
- Improved http client: RxHttpClient
- RxHttpClient uses chunked transfer-encoding only when content-length is NOT specified.
Migration guide
All CbsClient
methods gets CbsRequest
as a first parameter instead of RequestDiagnosticContext
. The CbsRequest
may be created by calling CbsRequests
factory methods. For existing code to work you will need to do the following change:
Code Block | ||
---|---|---|
| ||
// From this:
CbsClientFactory.createCbsClient(env)
.flatMap(cbsClient -> cbsClient.get(diagnosticContext))
...
// To this:
final CbsRequest request = CbsRequests.getConfiguration(diagnosticContext);
CbsClientFactory.createCbsClient(env)
.flatMap(cbsClient -> cbsClient.get(request))
... |
The similar changes will be required for other CbsClient
methods (periodic get and periodic updates).
✔ 1.1.3 (initial release)
...
- basic functionality
- CBS service discovery
- get application configuration as JsonObject
- periodic query + periodic updates query
...
Click here to see DCAE SDK Changelog