Fix#832#752
Adds caching capabilities to the converter. Remote calls to the
registry, Schema Parsing and toString were very expensive operations
that are now being cached
Adds a decorator to the registryClient that allows caching of remote
invocations.
Fixing review comments
Fixes#751
- Use Reactor 3.0.4.RELEASE
- Remove Scheduler implementations that were introduced for fixes
- Shade `io.reactivex:rxjava-reactive-streams` classes to replace removed RxJava1 adapter support
Signed-off-by: Marius Bogoevici <mbogoevici@pivotal.io>
Fixes#446
Supports properties prefixed with `spring.cloud.stream.default`
for specifying default values for large number of channels or
for dynamically generated channels.
Note: this does not cover binding specific properties,
as the property objects are created under binder's control
but the same technique can be applied there.
Rework default property binding
Minor: javadoc
Updated documentation
Renamed Table from Schema to SCHEMA_REPOSITORY to avoid potential reserved word clashes with some databases
Postgresql GH-696 requires transactional semantics even for reading operations when using Lob columns
Removed dependency to h2 database. A database driver is now explicitly required when running the server
Resolves#696 and #697
Resolves#691
- If the broker supports native serialization, then the serialization of the
outbound payload is not done by the binder's producer binding outbound message handler.
- At the consumer binding's inbound message handler, the extraction of embedded headers
is performed only for the byte[] payload (given the deserialization would have already
occurred at the broker level)
- Add correspoinding tests in Kafka binder implementation
- Rely on the received message type to decide on using out of the box deserializer (only
if byte[] message payload is received)
- This will avoid other lifecycle beans inside the application context starting when
binding lifecycle beans are started.
Resolves#525
Address review comments
