The overview doc gets unncessarily copied to the GitHub
repository root README. This only needs to reside in the
reference manual docs. Cleaning the process that generates
the root README for the repository.
* GH-1140: CommonErrorHandler per consumer binding
Setting CommonErrorHandler on consumer binding through its bean name.
If present, binder will resolve this bean and assign it on the listener
container.
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1140
* Addressing PR review
* Honoring auto startup in Kafka Streams binder
When using Kafka Streams bineder, the processors are started
unconditionally, i.e. autoStartup is always true by default.
If spring.kafka.streams.auto-startup is set, then honor that
as the auto-startup flag in the binder.
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1126
* Addressing PR review comments
Auto startup flag is honored per individual consumer bindings as well.
* Addressing PR review comments
* Making KafkaStreamsRegistry#kafkaStreams set to use a concurrent Set.
At the moment, Kafka Streams binder only allows KStream bindings on the outbound.
There is a delegation mechanism in which we stil can use KStream for output binding
while allowing the applications to provide a KTable type as the function return type.
Update docs.
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1085Resolves#1105
Composed function defintions can start with a `java.util.function.Function`
or `java.util.function.BiFunction` and compose with other functions or consumers.
In the case of a consumer, this needs to be the last unit in the function definition.
`java.util.function.BiConumer` is not eligibe for function composition.
The first component in the definition can be a curried function as well.
Adding tests and docs.
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1088Resolves#1091
* Kafka Streams function detection improvements
Allow Kafka Streams functions defined as Component beans
to be candidates for establishing bindings. Currently, Kafka Streams
functions need to be written as functional beans using @Bean.
Adding this improvement so that if applications prefer to write
the business logic using @Component, then it is possible to do so.
Adding test cases to verify the behavior.
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1030
* Kafka Streams functions and bean name overriding
Whn Kafka Streams function bean names are overridden,
there is an issue with scanning it properly for binding.
Addressing this issue.
* Adding docs for Component based model
* Addressing PR review comments
