* KafkaStreams Functions Detection Logic
Kafka Streams functions declared in super classes are no longer
detected by the binder discovery algorithms. Fixing this issue
by properly scanning the methods from the super classes.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2737
* Addressing PR review
* GH-2729: Reactor Kafka Binder SenderResult Support
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2729
Allow configuration of a `FluxMessageChannel` to receive `SenderResult`s.
Add `SenderResultMessageHandler` to consume from that channel.
Remove undocumented `sendResult` header, which has no value without the
sender result correlation metadata.
* Add integration test and polish property docs.
- result channel must be FMC for reactive binder.
* Add documentation.
* Remove SenderResultMessageHandler.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2706
- Update partition count changes in Kafka dynamically during runtime
- Checkstyle fixes
- PartitionHandler changes
- Improved handling of expression with 'payload' in the logic
- Removed getter/setter for PartitionHandler and use ReflectionUtils within Test
- Renamed property to 'dynamicPartitionUpdatesEnabled' and improved documentation (also one line per sentence)
- Improved/renamed test to use embeddedkafka and really test update behaviour
- Javadoc
Latest version of Mockito (5.3.0) used in Spring Boot 3.1.0,
apparently needs the specific Collection type when capturing
values via the ArgumentCaptor. Earlier versisons didn't mandate this.
* Port "Use builder to autoconfigure PulsarProducerFactory"
- Syncs changes from spring-pulsar/0.2.x/8bee5ef6e907b80933419f639f9f1bb6a3669ec5
* Port "Use builder to autoconfigure PulsarConsumerFactory"
- Syncs changes from spring-pulsar/0.2.x @ 82458872b52024f5464e677bf21763ccf564c0d2
* Port "Use builder to autoconfigure PulsarAdministration"
- Syncs changes from spring-pulsar/0.2.x @ d38cc6cb8d1a1d12499e302cbee75c00211e3537
When destination is pattern, even when the cluster is down,
health indicator is erroneously reporting the status as UP.
Addressing this issue by calling a simple listTopics on the
consumer when the destination is pattern, and if it throws an
exception, report the status as DOWN. If the call succeeds, we
assume that the cluster is accessible.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2628
* Event type routing and deserialization issues
In Kafka Streams binder, deserialization exception handler
does not take effect when event type routing is enabled.
Fixing this issue by allowing the applications to use the
configured or inferred Serde rather than the byte[] Serde
used by the event type router initially.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2613
* Addressing PR review
