Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Rapid table and database searches are not debounced

Open
#4,411 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@hutiefang76 is already working on this.

Since Oct 4, 2026.

  • #4414 by @hutiefang76 — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
frontend

Research direction

Start at the dashboard table/database menu and the regression runner that mounts the TablesMenu setup with fake timers. Run the five reported cases and verify that rapid input makes one request for the final keyword, clearing replaces pending work, and unmounting cancels callbacks.

Written by the indexing model from the issue text.

Description

type:bug
What happened?

Rapid typing schedules one search per input event because each event creates a separate debounce wrapper. Clearing the field leaves earlier callbacks pending, and pending callbacks survive component unmount.

Expected: one request for the final keyword per field after 300ms; clear replaces the pending search; unmount cancels callbacks that have not run.

Affects Versions

master at 061eb724e93592fe87cf44b61af34c1d799f5db6

What table formats are you seeing the problem on?

No response

What engines are you seeing the problem on?

No response

How to reproduce
  1. Open the dashboard table/database menu.
  2. Type several characters into either search field within 300ms.
  3. Inspect the search requests: every pending callback runs instead of only the last.
  4. Repeat while clearing the field or leaving the view before 300ms. Earlier pending callbacks still run.
Relevant log output

Anything else

The regression runner compiles and mounts the actual TablesMenu setup with fake timers. All five cases fail on the base and pass with per-instance timers and unmount cleanup. A tested fix is ready in hutiefang76/amoro branch fix/table-menu-search-debounce.

Are you willing to submit a PR?
  • Yes I am willing to submit a PR!
Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Java
Stars
1.2k
Forks
397
Avg merge
1d 21h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/amoro

All issues in apache/amoro

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.