feat: streaming CSV and Parquet export for transfers#149
Open
temisan0x wants to merge 1 commit into
Open
Conversation
- Add GET /transfers.csv and GET /transfers.parquet - Cursor-based batch fetching (500 rows/batch) keeps memory flat at any scale - CSV streams directly into response via @fast-csv/format - Parquet writes to tmp file then pipes to response, cleaned up after send - Both endpoints accept the same query params as the transfers route (address, contractId, fromLedger, toLedger, fromDate, toDate, eventType)
|
@temisan0x Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Closes #134
Adds GET /transfers.csv and GET /transfers.parquet. Both accept the same
filter params as the existing transfers route (address, contractId,
fromLedger, toLedger, fromDate, toDate, eventType) so analysts can slice
the data before exporting.
The main consideration was memory. Loading 1M rows before serializing would
kill the server, so both endpoints use a cursor loop — 500 rows per DB
round-trip, streaming out as we go. CSV pipes directly into the response via
@fast-csv/format. Parquet can't do the same (it needs to write a footer at
the end), so that one writes to a temp file first, pipes to the response,
then cleans itself up.
Tested manually against a local DB. Both endpoints complete without memory
spiking.