mostafa / xk6-kafka / 34229327639

78%

push

github

feat: initialize consumer groups at current end offsets (#412)

* feat: initialize consumer groups at current end offsets

* fix: harden consumer group offset initialization

- Drop the ConsumerGroupOffsetsConfig godoc misplaced above the
  AdminClient type (the type is declared in consumer_group_offsets.go).
- Compare committed offsets against the snapshot in
  validateAlteredConsumerGroupOffsets, not just partition presence.
- Map the broker non-empty-group error to a message that says the
  consumer group is still active.
- Wrap static sentinel errors instead of dynamic fmt.Errorf (err113).
- Mock-cluster test now also asserts that no historical records remain
  after the post-snapshot record is consumed.
- Integration script produces the historical record with the JSON serde
  and explicitly asserts no consumed message has kind "historical".
- Document the 2^53 JavaScript number precision limit for offsets.

* docs: regenerate api-docs v2 markdown

Output of yarn --cwd api-docs run generate-docs:v2: adds the
initializeConsumerGroupOffsets section to AdminClient.md, adds pages for
the ConsumerGroupOffsetsConfig and ConsumerGroupOffset interfaces, and
refreshes line references.

* fix: retry offset listing while partition leadership settles

ListOffsets right after topic creation can fail with
NOT_LEADER_FOR_PARTITION (or LEADER_NOT_AVAILABLE, UNKNOWN_TOPIC_OR_PART,
REPLICA_NOT_AVAILABLE) while leadership propagates, which failed the
consumer_group integration script in CI. Retry with linear backoff,
bounded by a max attempt count and the caller's context. Topic existence
is still validated up front by GetMetadata, so misspelled topics fail
immediately instead of being retried.

---------

Co-authored-by: Mostafa Moradian <mstfmoradian@gmail.com>

167 of 240 new or added lines in 2 files covered. (69.58%)

4056 of 5180 relevant lines covered (78.3%)

32.19 hits per line