That sound like expected. Note, if you use exactly-once, on commit/abort
of a transaction, the broker write a commit/abort message into the
partitions. Those markers fill up one message/record slot.
Thus, you have "gaps" in the message offsets and in you case, I assume
that you have 5 commit marke
Hello, i have following problem with kafka-streams scala app and Exactly
once delivery quarantee:
Topic filled with kafka-streams app(exactly once enabled) has wrong ending
offset. Broker and streams API version 0.11. When i run
*kafka.tools.GetOffsetShell*, it gives ending offset 17, but in top