provectus/kafka-ui

Brokers: Search of configs is working only for current page

Open

#3,347 建立於 2023年2月15日

在 GitHub 查看
 (4 留言) (0 反應) (1 負責人)Java (7,799 star) (977 fork)batch import
good first issuescope/backendseverity/mediumstatus/acceptedtype/enhancement

描述

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

貢獻者指南

技術棧
javareact
領域
frontend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
React knowledgePagination conceptsJava backend familiarityKafka UI codebase structure
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
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.
Brokers: Search of configs is working only for current page · provectus/kafka-ui#3347 | Good First Issue