Skip to content

GH-4369: Pass explicit acknowledgment mode as consumer override property#4374

Closed
maxwell-balla wants to merge 1 commit into
spring-projects:mainfrom
maxwell-balla:GH-4369
Closed

GH-4369: Pass explicit acknowledgment mode as consumer override property#4374
maxwell-balla wants to merge 1 commit into
spring-projects:mainfrom
maxwell-balla:GH-4369

Conversation

@maxwell-balla

Copy link
Copy Markdown
Contributor

Fixes #4369
When "setExplicitShareAcknowledgment(true)" is set on the container properties, the "share.acknowledgement.mode=explicit" property is now passed to the consumer factory via a new "createShareConsumer" overload that accepts override properties, instead of relying on the user to set it manually in the factory configuration.

Signed-off-by: Maxwell Balla ballamaxwell7@gmail.com

… override property

  Fixes spring-projects#4369
  When "setExplicitShareAcknowledgment(true)" is set on the container properties, the "share.acknowledgement.mode=explicit" property is now passed to the consumer factory via a new "createShareConsumer" overload that accepts override properties, instead of relying on the user to set it manually in the factory configuration.

  Signed-off-by: Maxwell Balla <ballamaxwell7@gmail.com>
@sobychacko

Copy link
Copy Markdown
Contributor

@maxwell-balla Thanks for the PR! We made some bigger refactoring and certain semantic changes in the way Share Consumers are acknowledged in 4.1. See the PR here: #4376. The gist is that EXPLICIT ack mode is the default going forward. Because of that, we are trying to deprecate the setter method on the ContainerProperties. Depending on how that PR progresses, the changes over there might supercede the changes in this PR. But we will let you know once we have a clarity on this matter.

@maxwell-balla

Copy link
Copy Markdown
Contributor Author

Thanks for the context @sobychacko

Making EXPLICIT the default in 4.1 makes a lot of sense, it's the safer behavior for most use cases.

Happy to close this PR if #4376 covers it. Either way, glad the issue got attention.

Also, feel free to point me to any other issues where a community contribution would help.
I'd be glad to pick them up.

@sobychacko

Copy link
Copy Markdown
Contributor

@maxwell-balla We will let you know soon on the status of this PR. In the meantime, feel free to pick up any of these open issues slated for the 4.1.0-RC1 release: https://github.com/spring-projects/spring-kafka/milestone/291. We need to tackle all of them ideally by the RC1 timeframe. Some of them are PR's or issues that are being worked on currently, but plenty of open ones that still need attention. If you decide to work on any issues, please ping us on the issue, so that we could avoid double work. Thanks for the help, really appreciated!!

@sobychacko

Copy link
Copy Markdown
Contributor

@maxwell-balla Now that PR #4376 is merged upstream, we are going to close this PR since the former one addresses the fixes here. Thank you for your efforts and feedback!

@sobychacko sobychacko closed this Apr 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants