apache / apache/beam

Kafka Streams runner: committed metrics

Open
#39,635 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

The Kafka Streams runner reports only attempted metric values. `MetricResults` exposes what the SDK harness reported per bundle, folded into the job's step map, with no committed variant, and `UsesCommittedMetrics` is excluded from the ValidatesRunner suite.

Committed metrics would need the metric updates to be committed atomically with the records and offsets of the bundle that produced them.

Part of #18479.

Contributor guide

Open the contributing guide

Research direction

Start by tracing MetricResults and the Kafka Streams runner's bundle handling, then inspect UsesCommittedMetrics and the ValidatesRunner suite. Determine how metric updates can be committed atomically with each bundle's records and offsets; done means committed metrics are exposed and the suite covers them.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, kafka
Domain
stream-processing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.