[SPARK-48061][SQL][TESTS] Parameterize max limits of spark.sql.test.randomDataGenerator
#46305
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 changes were proposed in this pull request?
This PR aims to parameterize
MAX_ARR_SIZE
,MAX_MAP_SIZE
, andMAX_STR_LEN
ofspark.sql.test.randomDataGenerator
by supporting.spark.sql.test.randomDataGenerator.maxArraySize
spark.sql.test.randomDataGenerator.maxMapSize
spark.sql.test.randomDataGenerator.maxStrLen
Why are the changes needed?
Apache Spark already has the code which needs these parameters. We had better support these to allow the developers to use them without changing and recompiling the source code.
spark/sql/core/src/test/scala/org/apache/spark/sql/streaming/StreamingQueryHashPartitionVerifySuite.scala
Lines 155 to 156 in 0329479
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual.
BEFORE (golden file size:
269M
)AFTER (golden file size:
5.8M
)Was this patch authored or co-authored using generative AI tooling?
No.