You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Arun sethia (Jira)" <ji...@apache.org> on 2024/06/20 17:05:00 UTC

[jira] [Updated] (SPARK-48674) Refactor SparkConnect Service to extracted error handling functions to trait

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

Arun sethia updated SPARK-48674:
--------------------------------
    Affects Version/s:     (was: 3.5.0)
                           (was: 3.5.1)

> Refactor SparkConnect Service to extracted error handling functions to trait
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-48674
>                 URL: https://issues.apache.org/jira/browse/SPARK-48674
>             Project: Spark
>          Issue Type: Improvement
>          Components: Connect
>    Affects Versions: 3.4.2, 3.4.0, 3.4.1, 3.4.3
>            Reporter: Arun sethia
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Since SparkConnect gRPC server can have multiple services (addService function on NettyServerBuilder) and these functions can be reused across services, specially when we would like to extend sparkconnect with various services.
> We can extract error handling functions from SparkConnectService to a trait, that will increase code reusability. By doing this we can reuse these functions across multiple service implementations. Since we can add multiple Bindable service handlers to SparkConnect gRPC server it will be easy to use such common functions to handle errors and exceptions.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org