apache/pinot

Handle change in default groupId behavior in kafka consumer

Open

#9,183 opened on Aug 9, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (1,234 forks)batch import
good first issue

Repository metrics

Stars
 (4,937 stars)
PR merge metrics
 (Avg merge 6d 7h) (186 merged PRs in 30d)

Description

Starting kafka 2.2.0 onwards, when group.id is not specified in the kafka consumer config, it is set as null, instead of an empty string. Due to this change, even though auto-commit is enabled, it doesn't show up in the consumer offsets topics. This breaks existing kafka monitoring tools.

One proposed solution is for Pinot to set a default group id when it was not explicitly configured by user (say, table name as the default group id).

Contributor guide

Research direction
Investigate where to set a default group.id in the Kafka consumer configuration, likely in the consumer creation logic within Pinot's codebase.
Tech stack
java
Domain
backenddata
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KafkaJavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65