provectus/kafka-ui

Topic page: Show N/A placeholder if there is not offset info available

Open

#3617 opened on Apr 3, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (7,799 stars) (977 forks)batch import
good first issuescope/frontendstatus/acceptedstatus/confirmedtype/bug

Description

Setup: topic page, BE returns null min/max offsets. Current behavior: Min and Max offsets not shown, Messages count is 0 (which is invalid)

Expected:

  • if either max or min offsets are unknown then Messages count should show N/A
  • if one of offset not available, then corresponding column should have N/A values

Contributor guide

Tech stack
reactjava
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
ReactKafka UI frontend
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Find the topic page React component that renders the min/max offsets and messages count. When the offset value is null, display 'N/A' instead. No linked PRs or discussion indicate a specific implementation; the fix is straightforward conditional rendering.