Skip to content

Support transactions, better listener names in config #564

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

Merged
merged 1 commit into from
Apr 20, 2025

Conversation

erikvanoosten
Copy link
Contributor

@erikvanoosten erikvanoosten commented Apr 20, 2025

Transactions are now possible; by changing the config a single broker is now enough.

The listener names in the broker config can be anything. What most people do (use the protocol name) is very confusing. Instead, we use the role of the listener.

Transactions are now possible; by changing the config a single broker is now enough.

The listener names in the broker config can be anything. What most people do (use the protocol name) is very confusing. Instead, we use the role of the listener.
@gaeljw
Copy link
Contributor

gaeljw commented Apr 20, 2025

LGTM. I'll let you merge and release :)

@erikvanoosten erikvanoosten merged commit b95f1df into master Apr 20, 2025
3 checks passed
@erikvanoosten erikvanoosten deleted the support-tx branch April 20, 2025 19:01
@gaeljw
Copy link
Contributor

gaeljw commented Apr 20, 2025

@erikvanoosten , FYI I think this repo used to align its version on the Kafka server one and only increase the 4th number to publish changes if the Kafka version hasn't changed in the meantime.

It could have been a 4.0.0.1 rather than 4.0.1.

I guess that's really not a big deal though. IMHO, we should keep the alignment on the major.minor though. Easier for users to track.

@erikvanoosten
Copy link
Contributor Author

Ah, I didn't know that. I'll keep it in mind for the next time.

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