Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose ack_fun through the init_info #591

Merged
merged 1 commit into from
Jul 2, 2024
Merged

Conversation

indrekj
Copy link
Contributor

@indrekj indrekj commented Jul 2, 2024

commit_fun is already exposed, but ack_fun is not. This is useful when acking does not happen inside the worker process.

E.g. We divide messages between multiple processes and later in a separate process we create a transaction and commit a batch. Now we need to let the consumer know that it's okay to fetch more messages.

I briefly considered adding tests for this but wasn't sure how to do it. I've manually tested it, and it works. It follows the same pattern as commit_fun.

`commit_fun` is already exposed, but `ack_fun` is not. This is useful
when acking does not happen inside the worker process.

E.g. We divide messages between multiple processes and later in a
separate process we create a transaction and commit a batch. Now we need
to let the consumer know that it's okay to fetch more messages.
@zmstone zmstone merged commit 74f8e5c into kafka4beam:master Jul 2, 2024
14 checks passed
@zmstone
Copy link
Contributor

zmstone commented Jul 2, 2024

thank you for the pr.

@zmstone
Copy link
Contributor

zmstone commented Aug 12, 2024

thank you. included in release 4.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants