provectus/kafka-ui

SR: Extend the search by field set

Open

#3170 opened on Dec 28, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (7,799 stars) (977 forks)batch import
good first issuescope/backendscope/frontendstatus/acceptedtype/enhancement

Description

Describe the bug

  1. Search only possible by the Schema name.
  2. Column name Subject doesn't match the "Schema name" used in the search.

Expected behavior

  1. Extend the search from "Subject" to "Subject", "ID", "Type"
  2. Rename the mask in the search, so there will be either "Schema name" or "Subject" both in the column names and search field hint.

Set up

f4e6afe

Steps to Reproduce

  1. Log in to Kafka UI and navigate to the Schema registry.

Screenshots

image

Additional context

@Haarolean requested to create a separate issue from the #2651

Contributor guide

Tech stack
None
Domain
frontenddata
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.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Kafka UI codebaseFamiliarity with schema registry
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue is to extend the search field set in the Schema Registry UI from only 'Subject' to include 'ID' and 'Type'. The search mask should be renamed to match the column names. Look at the React component responsible for the schema registry search. It likely uses a filter input. Review the existing search implementation and add the additional fields. Also ensure the placeholder text is consistent with column headers. The issue was split from #2651, which may contain more context. Start by finding the search component in the codebase, possibly under the schema registry directory.