feat: raise row page-size cap from 200 to 1000#59
Merged
gordonmurray merged 1 commit intoJun 11, 2026
Conversation
A developer asked for larger pages when reviewing data integrity across a table. The cap lived in two places: MAX_LIMIT in the backend (applied to /rows and /vector/preview) and the page-size dropdown in the frontend. Raise MAX_LIMIT to 1000 and add 500 and 1000 options to the dropdown. The default stays at 50. Vector cells keep their existing sparkline truncation, so the per-cell payload is unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A developer mentioned the viewer stops at 200 rows per page and asked for 500 or 1000 when reviewing data integrity across a table.
The cap lived in two places:
backend/app.py:MAX_LIMIT = 200, applied to thelimitparam on/datasets/{name}/rowsand/datasets/{name}/vector/preview. Anything over 200 returned a 422.web/vanilla/index.html: the page-size dropdown topped out at 200.This raises
MAX_LIMITto 1000 and adds 500 and 1000 options to the dropdown. The default stays at 50.I kept a ceiling rather than removing it. Each response serializes the whole page from PyArrow to JSON in one go, and vector columns can be large, so unbounded pages would be easy to misuse on wide tables. Vector cells keep their existing sparkline truncation, so the per-cell payload is unchanged.
Updated the limit-bounds test to check the new boundary (1000 accepted, 1001 rejected) and added a changelog entry. Ran the test suite against the 0.33.0 image and it passes.
Fixes #58