test(data:export): add NUTs for big exports #1145
Open
Conversation
This file contains 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
cristiand391
commented
Dec 9, 2024
| @@ -55,6 +58,34 @@ describe('data export bulk NUTs', () => { | |||
| await validateCsv(path.join(session.dir, 'data-project', outputFile), 'COMMA', ensureNumber(result?.totalSize)); | |||
| }); | |||
|
|
|||
| it('should export +1 million records in csv format', async () => { | |||
| const outputFile = 'export-scratch-info.csv'; | |||
| const command = `data export bulk -q "select id,ExpirationDate from scratchorginfo" --output-file ${outputFile} --wait 10 --json -o ${na40username}`; | |||
There was a problem hiding this comment.
query scratchorginfo records in our na40 hub:
➜ plugin-data git:(cd/large-bulk-export-nut) sf data query -q 'select count() from scratchorginfo' -o na40
Total number of records retrieved: 1622618.
cristiand391
commented
Dec 9, 2024
| } | ||
| ); | ||
| const fieldsRes = await exec(`jq 'map(${props.map((field) => `has("${field}")`).join(' and ')}) | all' ${filePath}`, { | ||
| shell: 'pwsh', |
There was a problem hiding this comment.
small refactor to remove hardcoded fields in the jq query, the caller can now pass them as an array of string. No functional changes.
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 PR do?
follow up to #1140
Adds 2 test cases to cover big data exports (+1 million records) where the API splits results in multiple batches, covering both CSV and JSON output formats.
What issues does this PR fix or reference?