Artem Bilan

See more info here: https://github.com/spring-projects/spring-integration/issues/3095. We probably really talk about the same matter - `lease`, `TTL` - should lend at the same functionality in the target lock implementation. Not sure...

I think we applied the renewal logic on the `CREATED_DATE` to avoid breaking changes in the minor release. For version 6.0 we definitely can consider to to have a new...

Yes, that makes sense. Thanks. We have renewal contract on the registry at the moment because of to big breaking change with a new `DistributedLock` abstraction. We will revise it...

See my previous comment: > because of to big breaking change with a new `DistributedLock` abstraction. We will revise it the next version. So, we are going to tackle this...

No, we didn't have a chance to look into this. So, it is unlikely this will make it into the current `6.0 RC1` in two weeks. Feel free to contribute...

> I'm reading off of an SQS queue and as soon as I get a message I send it to a Spring Integration Channel which is backed by a Redis...

I probably miss something from your explanation. Here is a simple unit test to play with: ``` @Test public void testMessagingAwareMapperForSerializationFeature() throws JsonProcessingException { ObjectMapper mapper = JacksonJsonUtils.messagingAwareMapper(); // mapper.disable(SerializationFeature.FAIL_ON_EMPTY_BEANS);...

Closed as `Invalid` without reporter response.

That's not correct. We have an extension project for exactly this one: https://github.com/spring-projects/spring-integration-extensions/tree/main/spring-integration-cassandra. And it is indeed reactive one. There is probably just need to move it to this project...

Fixed via: https://github.com/spring-projects/spring-integration/commit/a08713fe874131a41cb9191cd7c8d04ed0d03574