- 30 3月, 2022 2 次提交
-
-
由 Soby Chacko 提交于
-
由 Soby Chacko 提交于
-
- 23 2月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
Temporily downgrade SK to 3.0.0-M1 and Kafka client to 3.0.0
-
- 16 2月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
-
- 07 2月, 2022 1 次提交
-
-
由 Gary Russell 提交于
Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1195 Remove obsolete documentation. **cherry-pick to 3.2.x**
-
- 27 1月, 2022 10 次提交
-
-
由 Soby Chacko 提交于
This reverts commit 65960e10.
-
由 Soby Chacko 提交于
This reverts commit 01dbb493.
-
由 Soby Chacko 提交于
This reverts commit d2c12873.
-
由 buildmaster 提交于
-
由 buildmaster 提交于
-
由 Oleg Zhurakousky 提交于
-
由 Oleg Zhurakousky 提交于
This reverts commit 4cbcb404.
-
由 Oleg Zhurakousky 提交于
This reverts commit a25e2ea0.
-
由 Oleg Zhurakousky 提交于
This reverts commit 69e377e1.
-
由 Jay Lindquist 提交于
It looks like this has been incorrect for a few versions. The main branch is currently pulling in 3.1.0 https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/blob/main/pom.xml#L26
-
- 26 1月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
Test changes
-
- 24 1月, 2022 1 次提交
-
-
由 Rex Ijiekhuamen 提交于
-
- 20 1月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
-
- 19 1月, 2022 3 次提交
-
-
由 Soby Chacko 提交于
-
由 Soby Chacko 提交于
-
由 Soby Chacko 提交于
-
- 14 1月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
Currently, KafkaBinderHealthIndicator is not customizable and included by default when Spring Boot actuator is on the classpath. Fix this by allowing the application to provide a custom implementation. A new marker interface called KafkaBinderHealth can be used by the applicaiton to provide a custom HealthIndicator implementation, in which case, the binder's default implementation will be excluded. Tests and docs changes. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1180
-
- 13 1月, 2022 2 次提交
-
-
由 Soby Chacko 提交于
Currently, KafkaBinderHealthIndicator is not customizable and included by default when Spring Boot actuator is on the classpath. Fix this by allowing the application to provide a custom implementation. A new marker interface called KafkaBinderHealth can be used by the applicaiton to provide a custom HealthIndicator implementation, in which case, the binder's default implementation will be excluded. Tests and docs changes. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1180
-
由 Soby Chacko 提交于
Fixing checkstyle issues.
-
- 12 1月, 2022 4 次提交
-
-
由 Soby Chacko 提交于
InteractiveQueryService methods for finding the host info for Kafka Streams currently throw exceptions if the underlying KafkaStreams are not ready yet. Introduce a retry mechanism so that the users can control the behaviour of these methods by providing the following properties. spring.cloud.stream.kafka.streams.binder.stateStoreRetry.maxAttempts (default 1) spring.cloud.stream.kafka.streams.binder.stateStoreRetry.backoffPeriod (default 1000 ms). Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1185
-
由 Soby Chacko 提交于
InteractiveQueryService methods for finding the host info for Kafka Streams currently throw exceptions if the underlying KafkaStreams are not ready yet. Introduce a retry mechanism so that the users can control the behaviour of these methods by providing the following properties. spring.cloud.stream.kafka.streams.binder.stateStoreRetry.maxAttempts (default 1) spring.cloud.stream.kafka.streams.binder.stateStoreRetry.backoffPeriod (default 1000 ms). Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1185
-
由 Eduard Domínguez 提交于
checkstyle fixes
-
由 Eduard Domínguez 提交于
checkstyle fixes
-
- 08 1月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
Fixing Kafka Streams composition tests due to an application.id issue.
-
- 06 1月, 2022 2 次提交
-
-
由 Soby Chacko 提交于
When routing by event types, the deserializer omits the topic and header information. Fixing this issue. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1186
-
由 Soby Chacko 提交于
When routing by event types, the deserializer omits the topic and header information. Fixing this issue. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1186
-
- 05 1月, 2022 1 次提交
-
-
由 Soby Chacko 提交于
-
- 04 1月, 2022 8 次提交
-
-
由 Soby Chacko 提交于
-
由 Soby Chacko 提交于
4.0.0-SNAPSHOT Spring Kafka - 3.0.0-SNAPSHOT Spring Integraton Kafka - 6.0.0-SNAPSHOT Spring Cloud Stream - 4.0.0-SNAPSHOT Code changes for Jakarta
-
由 Eduard Domínguez 提交于
Use extended properties when initializing Consumer and Producer Serdes. Updated copyright years and authors. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1176
-
由 Soby Chacko 提交于
Allow health checks on KafkaStreams processors that are currently stopped through actuator bindings endpoint. Add this only as an opt-in feature through a new binder level property - includeStoppedProcessorsForHealthCheck which is false by default to preserve the current health indicator behavior. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1165 Resolves #1175
-
由 Soby Chacko 提交于
Migrate the recipe section in Spring Cloud Stream Samples repository as Tips, Tricks and Receipes in Kafka binder main docs. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1173 Resolves #1174
-
由 Soby Chacko 提交于
The newly added DefaultPartitioningInteceptor must be explicitly checked in order to avoid a CCE. Related to resolving https://github.com/spring-cloud/spring-cloud-stream/issues/2245 Specifically for this: https://github.com/spring-cloud/spring-cloud-stream/issues/2245#issuecomment-977663452
-
由 Soby Chacko 提交于
Move classpath: resources provided as schema registry certificates into a local file system location. Adding test and docs. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1170
-
由 Pommerening, Nico 提交于
This PR safe guards state store instances in case there are multiple KafkaStreams instances present that have distinct application IDs but share State Store Names. Change is backwards compatible: In case no KafkaStreams association of the thread can be found, all local state stores are queried as before. In case an associated KafkaStreams Instance is found, but required StateStore is not found in this instance, a warning is issued but backwards compatibility is preserved by looking up all state stores. Store within KafkaStreams instance of thread is preferred over "foreign" store with same name. Warning is issued if requested store is not found within KafkaStreams instance of thread. The main benefit here is to get rid of randomly selecting stores across all KafkaStreams instances in case a store is contained within multiple streams instances with same name. Resolves https://github.com/spring-cloud/spring-cloud-stream-binder-kafka/issues/1161
-