When using server-side pagination in a table chart, the search bar only filters the results visible on the current page, instead of searching across the entire dataset returned by the query. 📌 Steps to reproduce: Create a table chart with a dataset large enough to require pagination.
Enable server-side pagination.
Try to search for a value that exists on a different page (not currently visible).
The search input does not return any results unless the value is present in the currently displayed page.
🔎 Expected behavior: The search bar should filter the entire result set returned by the query, not just the current page.
Comment From: dosubot[bot]
Hello @ryepezb1! I'm Dosu, your friendly bot here to help you solve bugs, answer questions, and become a contributor while we wait for a human maintainer. Let’s tackle those issues together! 🚀
The current behavior of the search functionality in the table chart component with server-side pagination is designed to filter only the results visible on the current page. This is because the search functionality updates the query object with row_offset set to 0 when filters change, ensuring pagination resets to the first page. The search is integrated with server-side pagination by adjusting properties like row_limit and row_offset based on the current page and page size [1].
To achieve the expected behavior of searching across the entire dataset, you would need to modify the implementation to fetch and filter data from all pages on the server side, rather than just the current page. This would involve changes to how the query is constructed and how data is fetched from the backend.
To continue talking to Dosu, mention @dosu.
Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other
Comment From: msyavuz
I think this is an intended behavior but supporting both visible and full search could be an option. If you are interested in implementing this PR's are always welcome. But i am inclined to move this to discussion since it looks like a feature request.