[SPARK-53901][CONNECT] Handle potential memory leaks inSparkConnectAddArtifactsHandler
upon flush/error
#52610
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?
Close the streams and clear the
stagedArtifacts
buffer when it is no longer needed. Further, we explicitly attempt to close inner streams in case closing an outer stream (which generally cascades down) fails.Why are the changes needed?
Upon flushing artifacts (or on an error), we delete the files on disk but the buffer is never cleared (and potentially open file handles), despite not being required anymore. An optimisation here is to clear them without relying on GC
Does this PR introduce any user-facing change?
No.
How was this patch tested?
New unit tests.
Was this patch authored or co-authored using generative AI tooling?
Co-authored with assistance from Claude Code.