-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
Serde: Support __transaction_state
topic
#407
Comments
Hi ver-alex! 👋 Welcome, and thank you for opening your first issue in the repo! Please wait for triaging by our maintainers. As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues. If you plan to raise a PR for this issue, please take a look at our contributing guide. |
Further user feedback is requested. Please reply within 7 days or we might close the issue. |
Sorry, my bad. __consumer_offsets work as expected. Will amend the initial description. |
Thanks for the additional feedback! We'll get back to your issue soon. |
__transaction_state
and __consumer_offsets
__transaction_state
__transaction_state
__transaction_state
topic
Issue submitter TODO list
Is your proposal related to a problem?
I would like to be able to show content of the Kafka internal topics.
Describe the feature you're interested in
To get a better insight into the internal Kafka transactions topic
__transaction_state
it would be great to be able to show the key/value in a readable format. The necessary serdes/formatters should be available in the Kafka distribution/clients.Describe alternatives you've considered
We are currently using the
kafka-console-consumer.sh
with the formatter for transactions.$ kafka-console-consumer.sh --formatter "kafka.coordinator.transaction.TransactionLog\$TransactionLogMessageFormatter" --bootstrap-server localhost:29092 --topic __transaction_state --from-beginning
Version you're running
2956664 v1.0.0
Additional context
No response
The text was updated successfully, but these errors were encountered: