If kafka truststore and keystore locations are not local files, then they
are converted to org.springframework.core.io.Resource resources, then copied
to local file system. This means that, paths can be defined as HTTP resources too.
Currently, the Kafka binder only supports CLASSPATH based resources. It would be
useful if we can support non-CLASSPATH like resources such as HTTP, so that if an
application uses config server for example to store certificates, then those will
be copied from it's HTTP endpoint to the local filesystem as Resources.
Checkstyle, documentation fixes.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2761
There was a regression introduced in Spring Cloud Function where consumers
of type Consumer<Message<?>> receive null values when tombstone records
are given as KafkaNull.
See this issue for more details: https://github.com/spring-cloud/spring-cloud-function/issues/1060
Regression is addressed in Spring Cloud Function and
making the corresponding test changes in Spring Cloud Stream Kafka binder.
- Insted of unconditionally initializing KafkaJaasLoginModuleInitializer,
only create it, if jaas properties are set properly. By creating it always,
we unncessarily expose Java security related class requirements to the binder
apps. For e.g. if the underlying JVM security classes change and require
reflection, that could break AOT apps that don't use a secure Kafka cluster.
Fixing these type of issues by creating KafkaJaasLoginModuleInitializer only if required.
- Before running a test, invalidate any existing JVM-wide static
security configuration so that tests are forced to create/use
fresh security configuration. Without this, test suites with
multiple security tests might fail as they might overlap with
security confugiruation from other tests.
* Reactor Kafka Binder Health Indicator
- Provide a new abstraction for general Kafka binder related HealthIndicators.
- Refactor Kafka binder to use the new abstraction
- Add HealthIndicator implementation for the ReactorKafkaBinder
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2752
* Addressing PR review
* Addressing PR review
* Addressing PR review
- When using reactive functions, partition selector strategy does not
use the configured partition count for multiple outbounds. This is
because we take the first configured output binding and apply it's
partition counts on all the outbound reactive streams (Tuples).
Addressing this issue by properly applying the correct partition handling
per output binding.
Resolves https://github.com/spring-cloud/spring-cloud-stream/issues/2750
* 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.
