[
https://issues.apache.org/jira/browse/SPARK-44855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herman van Hövell resolved SPARK-44855.
---------------------------------------
Fix Version/s: 4.0.0
Assignee: Juliusz Sompolski
Resolution: Fixed
> Small tweaks to attaching ExecuteGrpcResponseSender to ExecuteResponseObserver
> ------------------------------------------------------------------------------
>
> Key: SPARK-44855
> URL: https://issues.apache.org/jira/browse/SPARK-44855
> Project: Spark
> Issue Type: Improvement
> Components: Connect
> Affects Versions: 4.0.0
> Reporter: Juliusz Sompolski
> Assignee: Juliusz Sompolski
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.0.0
>
>
> Small improvements can be made to the way new ExecuteGrpcResponseSender is
> attached to observer.
> * Since now we have addGrpcResponseSender in ExecuteHolder, it should be
> ExecuteHolder responsibility to interrupt the old sender and that there is
> only one at a time, and to ExecuteResponseObserver's responsibility
> * executeObserver is used as a lock for synchronization. An explicit lock
> object could be better.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
