provectus/kafka-ui

Brokers: Configs - No results matching 'Value' column value

Open

#4180 opened on Aug 31, 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

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running master-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

No results matching "null" by searching even if there are records with such value.

Expected behavior

All matching results based on key word in Search input should be displayed.

Your installation details

Running master-labeled docker image

Steps to reproduce

  1. Navigate to Brokers
  2. Click on any broker and switch to Configs tab.
  3. Search by "null" value

Screenshots

https://github.com/provectus/kafka-ui/assets/106804748/4511d6e6-f501-4882-9f2b-d9a997af8567

Logs

No response

Additional context

No response

Contributor guide

Tech stack
javareacttypescript
Domain
frontend
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.
1-3 hours
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
Familiarity with React and TypeScriptUnderstanding of frontend filtering logic
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Investigate the search functionality in the Brokers Configs tab. Look for the filter function that handles the search input. The issue is likely due to the search term 'null' being parsed as a null value rather than a string. Check the component files under the 'brokers' directory for the configs table filtering logic. Review any existing tests for this feature. Consider adding a test case for searching the literal string 'null'.