...
WARNING
This is a work in progress. Do not use unless you know what you are doing!
1.1.5
- TODO Piotr JaszczykDMaaP client
- Force non-chunked transfer encoding, because DMaaP MR does not support it.
- DMaaP MR client API should be used in new code. Some minor incompatible changes can occur but it's more or less done.
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 (
Sinks) and streams_subscribes (Sources) 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.
...