DrillDetailTable's pageSize is 50, but the pageSizeOptions allows the default 5,15,25,50,100

[durban77]

Bug description

On the Drill to details table of a chart, when you set the pageSize to lower than 50, you can overread the results by jumping to the last page. Also setting the pageSize to 100 only shows 50 rows.

The cause is that the pageSize is set to a constant value of 50, but the pageSizeOptions inherit a [5,15,25,50,100] valueset and the UI shows the pageSize as a user changeable value.

One possible solution is to set the pageSizeOptions to ['50'] because it is the only valid option right now. This will cause the pageSize selector to have only one value.
DrillDetailPane.tsx
defaultPageSize={PAGE_SIZE}
++ pageSizeOptions={['50']}

I'm happy to make the adjustment, but please someone approve this!

Screenshots/recordings

Superset version

master / latest-dev

Python version

I don't know

Node version

I don't know

Browser

Not applicable

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• 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.

[dosubot]

Hi @durban77! I'm Dosu and I’m helping the superset team.

You’re correct—DrillDetailTable always fetches and displays 50 rows per page, but the Table UI lets users pick other page sizes (like 5, 15, 25, 100), which causes bugs: selecting a different size either overreads results or only shows 50 rows regardless of the selection. This happens because the backend and cache logic are hardcoded to use PAGE_SIZE = 50, while the Table component defaults to pageSizeOptions = ['5', '15', '25', '50', '100'] and exposes the selector in the UI. The Table’s pagination handler doesn’t actually update the backend page size, so the UI and data get out of sync (source).

Setting pageSizeOptions={['50']} is a safe immediate fix—it removes the misleading selector and aligns the UI with what the backend supports (source). If you want users to be able to pick other page sizes, you’d need to refactor the DrillDetailPane logic to propagate the selected page size into the API call and cache logic, so the backend actually fetches the right number of rows per page.

No recent changes or planned fixes for this in master, and similar issues have been reported in other table visualizations. Your proposed adjustment is the right move unless/until variable page sizes are supported in the backend.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[tysoncung]

I'm interested in working on this issue. Could you provide more context about what you're looking for? Any additional details about requirements or constraints would be helpful.

[durban77]

I'm interested in working on this issue. Could you provide more context about what you're looking for? Any additional details about requirements or constraints would be helpful.

So the drill to details table has a fixed page size of 50 rows per page. Somehow, a page size selector appeared near the page picker part. It is misleading, because you cannot really change the page size, it is a fixed value. One solution (1) is to hide that component through css, one solution (2) is to have only the valid 50 option and there might be a solution (3) to make page size of 50 alterable by the user. First (1) and second option (2) is working, but more like a temporary fix.

By not fixing it, the user can set the page size

• bigger than 50, which appear as a bug that only 50 rows are displayed and the paging is still 50.
• less than 50, which appear as a bug that nonexisting pages appear and switching to the last page will be empty or a database query error (depending on the db engine)

So I've applied a quick fix for it (1) on my instance and shared my solution (2) as a PR for others.
But I think the community would like the proper (3) solution for this.

[aditikh-76]

Hi! I’d like to work on this issue. Could someone guide me on where the DrillDetailTable implementation is located?

[suyash-bodhane]

"Hello! I have attempted to resolve this issue and have recently raised a PR. Could you please review it and guide me on any further corrections or improvements related to issue #36267" ?

[aditikh-76]

Thanks for the update! I’ll look for another issue to work on.