Fix format violation in the TwitterGeoFunctionConfiguration

* Resolve TODO in the `DebeziumReactiveConsumerConfiguration`
This commit is contained in:
Artem Bilan
2024-12-19 13:16:24 -05:00
parent c5971241a7
commit 4024f19119
2 changed files with 2 additions and 5 deletions

View File

@@ -107,8 +107,7 @@ public class TwitterGeoFunctionConfiguration {
@Bean
public Function<Message<?>, Message<byte[]>> twitterGeoFunction(
Function<Message<?>, GeoQuery> messageToGeoQueryFunction,
Function<GeoQuery, List<Place>> twitterPlacesFunction,
Function<Object, Message<byte[]>> managedJson) {
Function<GeoQuery, List<Place>> twitterPlacesFunction, Function<Object, Message<byte[]>> managedJson) {
return messageToGeoQueryFunction.andThen(twitterPlacesFunction).andThen(managedJson);
}

View File

@@ -59,9 +59,7 @@ public class DebeziumReactiveConsumerConfiguration {
DebeziumMessageProducerSpec debeziumMessageProducerSpec = Debezium.inboundChannelAdapter(debeziumEngineBuilder)
.enableEmptyPayload(supplierProperties.isEnableEmptyPayload())
.headerNames(supplierProperties.getHeaderNamesToMap())
// TODO until Spring Integration 6.3.0-M2
.autoStartup(false);
.headerNames(supplierProperties.getHeaderNamesToMap());
if (debeziumMessageProducerSpecComponentCustomizer != null) {
debeziumMessageProducerSpecComponentCustomizer.customize(debeziumMessageProducerSpec);