Bug description
When utilizing the search bar functionality within a table in GitHub, the total calculation feature fails to adjust accordingly. This means that when searching for specific values within the table, the total calculation displayed does not reflect the filtered results, leading to inaccuracies in data analysis and reporting.
How to reproduce the bug
- Go to a Table that has a
Search barandShow Totalsenabled - Populate the table
- Perform a search using the search bar for specific values within the table. I used a ticketID
- Observe that the table adjusts to show only the rows matching the search criteria.
- Check the "Show Total" calculation displayed at the bottom of the numerical column.
- Note that the total calculation does not adjust to reflect the filtered results; it continues to display the total for all values, including those not visible due to the search filter.
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
When I conduct cross filtering
Checklist
- [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: rusackas
Ahh yes.. the crossfilter actually changes the data being fed to the table, so the total is calculated. The filter IN the table doesn't appear to recalculate on the fly. I'm sure it could if it had all the data, but if server pagination comes into play, that gets quite complicated.
Not sure if @justinpark 's planned migration to AG Grid would solve this.
Comment From: rusackas
This still seems to be the case, but the issue has gone silent for upward of a year. Anyone want to open a PR? If not, we may close this issue as stale in time.