feat: Update export_runs to use paginated API with disk-based exports #151
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.
Key Changes:
export_runs
to paginated endpoint for better performanceAdded:
format
andbase_dir
for export customizationChanged:
export_runs()
return type from DataFrame to directory path stringDocumentation Updates:
Generated Summary:
export_runs
method to handle pagination, ensuring all data is written to appropriately named files.format
andbase_dir
parameters in theexport_runs
method documentation.This summary was generated with ❤️ by rigging
This update significantly improves export performance for large datasets by leveraging server-side pagination and organized file-based storage, eliminating memory constraints while providing flexible output formats.