provectus/kafka-ui

Brokers: Search of configs is working only for current page

Open

Aperta il 15 feb 2023

Vedi su GitHub
 (4 commenti) (0 reazioni) (1 assegnatario)Java (7799 star) (977 fork)batch import
good first issuescope/backendseverity/mediumstatus/acceptedtype/enhancement

Descrizione

Describe the bug (Actual behavior) The configs search by key is available only for current configs page

Expected behavior The configs search should be done for all configs

Set up https://www.kafka-ui.provectus.io/

Steps to Reproduce

  1. Navigate to Brokers
  2. Select the Broker
  3. Turn to Configs tab
  4. Open the second page
  5. Search for config existing in first page

Screenshots

https://user-images.githubusercontent.com/104780608/218959611-275cfc21-fff6-4f30-8823-1fde662ea5f8.mov

Guida contributor

Tech stack
javareact
Dominio
frontend
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
blocked
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
React knowledgePagination conceptsJava backend familiarityKafka UI codebase structure
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
50
Direzione di ricerca
Investigate the configuration search functionality in the frontend (likely a React component) and the corresponding API endpoint in the backend. The bug suggests the search is only applied to the current page of results (client side pagination). Check if the search query is being sent to the backend with pagination parameters, and ensure the backend returns all matching configs regardless of page. Look at the code for 'configs' tab in the Brokers view, possibly in files related to 'KafkaBroker' or 'ConfigsList'. The existing assignee has likely started work; check comments for updates.