[SPARK-52409][SDP] Only use PipelineRunEventBuffer in tests #51352
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 inverts the relationship between event callbacks and
PipelineRunEventBuffer
.Prior to this PR:
PipelineUpdateContext
had aPipelineRunEventBuffer
, that all events from the run were written to.PipelineRunEventBuffer
contained aneventCallback
val which the Connect backend used to forward events to the clientAfter this PR:
PipelineUpdateContext
has aneventCallback
, which is invoked on all events.PipelineRunEventBuffer
and passes itsaddEvent
method to theeventCallback
Why are the changes needed?
With the prior code, there was a risk of memory pressure from the event buffer for long-running pipelines.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing tests
Was this patch authored or co-authored using generative AI tooling?
No