dosubot[bot] commented on issue #34102: URL: https://github.com/apache/superset/issues/34102#issuecomment-3048285811
<!-- Greeting --> Hi @aizeld! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> This looks like a known issue with server-side pagination in table visualizations—there have been recent reports where changing row limits or enabling server pagination causes the frontend table to not update correctly, even though the backend query and pagination controls reflect the right values. This is likely due to state synchronization problems between the frontend controls and the backend query logic, especially after recent updates to the table chart components and pagination controls [[example issue](https://github.com/apache/superset/issues/32513)]. Server pagination is implemented as an experimental feature and relies on the correct state being passed through several frontend components (control panel, TableChart, DataTable). Recent pull requests have changed how sorting and pagination controls work, which may have introduced regressions or subtle bugs [[PR #33540](https://github.com/apache/superset/pull/33540)]. A few things to check or try: - Make sure "Server pagination" is enabled in the chart controls and that "Server Page Length" is set to your desired value. - If the table doesn't update when you change the page or row limit, try toggling server pagination off and on, or refreshing the chart. - If you see a mismatch between the pagination controls and the data shown, it may be a state sync issue—this has been reported in recent versions and is under discussion [[related issue](https://github.com/apache/superset/issues/32513)]. If you can share the exact Superset version and describe the buggy behavior in more detail (e.g., what happens when you change pages or row limits), I can help pinpoint whether it's a regression from a specific update or a configuration issue. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9e6bc52f-3bad-42f5-8eb2-32b63df348c0?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/34102) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
