fix: provision-quality - set max plan strigh length - #96
Merged
Conversation
tombrooks248
marked this pull request as ready for review
July 24, 2026 08:12
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
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 type of PR is this? (check all applicable)
Description
Add
--conf spark.sql.maxPlanStringLength=8192to theprovision-qualityEMR Serverless job's spark-submit parameters.Why
provision-qualityjob was failing with a driver out-of-memory, despite processing only a small amount of data (~17 min job).*The query-plan string is just a human readable logging of the plan that pyspark is going to take as it completes its pyspark job, in this case the act of generating this string in an attempt to put it into the logs is, took up all the memory of the pyspark driver and resulted in the job failing.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Done a full test in Staging
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.
[optional] Are there any post deployment tasks we need to perform?
[optional] Are there any dependencies on other PRs or Work?