viirya opened a new pull request, #12:
URL: https://github.com/apache/spark-connect-gateway/pull/12
### What changes were proposed in this pull request?
Part of importing the Spark Connect Gateway reference implementation into
`apache/spark-connect-gateway` as a series of small, bottom-up PRs (tracked
in
the do-not-merge reference PR #1).
This adds two more crates that implement/wrap the `scg-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. 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.
### Why are the changes needed?
Implements the reference gateway from the approved SPIP (SPARK-58455),
imported
one reviewable piece at a time.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
`cargo fmt --all --check`, `cargo clippy --workspace --all-targets -- -D
warnings`,
`cargo build --workspace`, and `cargo test --workspace` all pass locally
(Redis integration tests are `#[ignore]`, so no Docker is required in CI).
### Was this patch authored or co-authored using generative AI tooling?
Yes, co-authored with Claude Code.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
