[ 
https://issues.apache.org/jira/browse/SPARK-49423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herman van Hövell resolved SPARK-49423.
---------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 47921
[https://github.com/apache/spark/pull/47921]

> Consolidate Observation into a single class in sql/api
> ------------------------------------------------------
>
>                 Key: SPARK-49423
>                 URL: https://issues.apache.org/jira/browse/SPARK-49423
>             Project: Spark
>          Issue Type: New Feature
>          Components: Connect, SQL
>    Affects Versions: 4.0.0
>         Environment: Not sure if we should do this. Connect and Classic have 
> different semantics, so unification is a bit tricky.
>            Reporter: Herman van Hövell
>            Assignee: Herman van Hövell
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> Move the implementation specific bits out of the class, and only keep the 
> Observation class. While we are at it, let's also replace the homegrown 
> threading stuff by futures.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to