You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[SPARK-52409][SDP] Only use PipelineRunEventBuffer in tests
### What changes were proposed in this pull request?
This PR inverts the relationship between event callbacks and `PipelineRunEventBuffer`.
Prior to this PR:
- `PipelineUpdateContext` had a `PipelineRunEventBuffer`, that all events from the run were written to.
- This `PipelineRunEventBuffer` contained an `eventCallback` val which the Connect backend used to forward events to the client
- The only code that reads from the buffer is test code
After this PR:
- `PipelineUpdateContext` has an `eventCallback`, which is invoked on all events.
- The test harness constructs a `PipelineRunEventBuffer` and passes its `addEvent` method to the `eventCallback`
### 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
This patch had conflicts when merged, resolved by
Committer: Sandy Ryza <sandy.ryza@databricks.com>
Closesapache#51352 from sryza/pipeline-run-event-buffer.
Lead-authored-by: Sandy Ryza <sandyryza@gmail.com>
Co-authored-by: Sandy Ryza <sandy.ryza@databricks.com>
Signed-off-by: Sandy Ryza <sandy.ryza@databricks.com>
0 commit comments