No need for 3000 row tests #8978
Merged
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
LARGE_NUMBER_OF_ROWS was set to 3000 in order to confirm that the queries related to user data export do not trigger full table scans for a large number of rows, but it's only necessary to have a non-zero amount of rows. Tune this down as it was causing tests to take a long time.
smklein
approved these changes
Sep 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
LARGE_NUMBER_OF_ROWS was set to 3000 in order to confirm that the queries related to user data export do not trigger full table scans for a large number of rows, but it's only necessary to have a non-zero amount of rows. Tune this down as it was causing tests to take a long time.