Add batchMode value in ContainerProperties
See original GitHub issueI want to get the batchMode value from ListenerContainerCustomizer.
But I can’t determine the batchMode from ContainerProperties .
Could you pass the extendedConsumerProperties' batchMode value to ContainerProperties ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Does spring Kafka batch listener commits db transaction in ...
I am using spring kafka in batch listener mode. I have gone through spring kafka docs but still its not clear that when...
Read more >Accessing and modifying model element properties
The container properties modification and iteration is straightforward using the java.util.Collection interface. Property change events are ...
Read more >ContainerProperties - AWS Batch
Container properties are used for Amazon ECS based job definitions. These properties to describe the container that's launched as part of a job....
Read more >Apache Kafka Support - Spring
It can accept values of record or batch (default: record ). For record mode, each message payload is converted from a single ConsumerRecord...
Read more >Randomly fail to create PublicIPAddress in batch mode #4531
My SDK version is 1.11.1, Newtownsoft.Json version is 11.0.2: "Microsoft.Azure.Management.Compute.Fluent" Version="1.11.1" "Microsoft.Azure.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This is not supported. The proper way to handle this is to configure 2 named binders, one transactional and one not transactional.
Then configure each binding with which binder to use.
@garyrussell Thanks, I will close this issue.