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

L. C. Hsieh resolved SPARK-59046.
---------------------------------
    Fix Version/s: connect-gateway-0.1.0
       Resolution: Fixed

Issue resolved by pull request 12
[https://github.com/apache/spark-connect-gateway/pull/12]

> Import scg-store-redis and scg-healthcheck crates into Spark Connect Gateway
> ----------------------------------------------------------------------------
>
>                 Key: SPARK-59046
>                 URL: https://issues.apache.org/jira/browse/SPARK-59046
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Connect
>    Affects Versions: connect-gateway-0.1.0
>            Reporter: L. C. Hsieh
>            Assignee: L. C. Hsieh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: connect-gateway-0.1.0
>
>
> Part of importing the Spark Connect Gateway reference implementation into
> apache/spark-connect-gateway as a series of small, bottom-up PRs.
> This adds two more crates that implement/wrap the routing traits, grouped into
> one PR:
>   
>   - scg-store-redis — a Redis-backed AffinityStore for cross-replica HA (the
>     multi-replica counterpart to the in-process scg-store-memory).
>   - scg-healthcheck — active gRPC health probing wrapped around a Pool, 
> evicting
>     unhealthy backends from routing.
> Both depend on the scg-routing crate (SPARK-58773). They compile and test on
> their own; store-redis's Redis integration tests are #[ignore] so they compile
> but don't require Docker in CI. Both are appended to the workspace members 
> list
> and are consumed later by the proxy crate (both are proxy dev-dependencies 
> used
> by its examples/tests). With this PR, all four proxy dev-dependency crates
> (store-memory, pool-static, store-redis, healthcheck) are in place, so the 
> proxy
> PR can follow.



--
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