hutiefang76 opened a new issue, #4411: URL: https://github.com/apache/amoro/issues/4411
### 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 ```shell ``` ### 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? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's Code of Conduct -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
