feat: Add optional take to DataFrame Service export table data request model #177
Conversation
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
spanglerco
requested review from
cameronwaterman and
rbell517
as code owners
spanglerco
commented
Dec 10, 2025
rbell517
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this Pull Request accomplish?
Python client support for restricting the number of rows returned by the export table data route. The default is to return all rows.
Why should this Pull Request be merged?
Enables using the export route as an undecimated dump of table data while restricting the number of rows to avoid retrieving more data than expected.
What testing has been done?
Tests pass. Ran the export_data example against a table with over 100,000 rows and verified the resulting CSV file only contained 100,000 rows.