A Kafka transaction can publish several records as one committed result. A read_committed consumer skips aborted records and waits at an unresolved transactional boundary rather than treating pending data as finished. Committing and aborting are different outcomes even if both let a producer move on. These exercises open a transaction, write a record, commit it and inspect it using the required isolation. The local controls make transaction state visible without running a Java producer. They model atomic visibility, not the full fencing, timeout or coordinator protocol. Before declaring success, check the transaction state and the consumer evidence. A record displayed in an uncommitted log view is not sufficient.
Inspect the topics, partition logs and group offsets before changing the cluster.