viirya opened a new pull request, #3:
URL: https://github.com/apache/spark-connect-gateway/pull/3

   ### 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 the `scg-routing` crate — the routing core of the gateway. It 
defines
   the central traits and types that the pool and store layers implement and 
that
   the proxy routes through:
   
   - `SessionKey` — the routing key derived from a request
   - `Pool` — the backend-pool trait (implemented later by pool-static / 
pool-k8s)
   - `AffinityStore` — the session-affinity store trait (implemented later by
     store-memory / store-redis)
   - `Router` — ties them together
   
   `scg-routing` is a leaf crate (no internal dependencies), so it compiles and
   tests on its own. It is appended to the workspace `members` list. Subsequent
   PRs add the crates that depend on it.
   
   ### 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
   (scg-routing has 15 unit tests).
   
   ### 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]

Reply via email to