[
https://issues.apache.org/jira/browse/SPARK-59145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
L. C. Hsieh resolved SPARK-59145.
---------------------------------
Fix Version/s: connect-gateway-0.1.0
Resolution: Fixed
Issue resolved by pull request 15
[https://github.com/apache/spark-connect-gateway/pull/15]
> Import gateway binary crate into Spark Connect Gateway
> ------------------------------------------------------
>
> Key: SPARK-59145
> URL: https://issues.apache.org/jira/browse/SPARK-59145
> 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 the gateway crate — the binary entry point that wires all the
> previously imported layers into a runnable server. It reads the YAML config
> (--config, default config.yaml), builds the chosen backend pool (static or
> Kubernetes service-watch) and affinity store (in-memory or Redis), installs
> the
> configured authenticator, tenant resolver, rate limiter, and audit sink, wraps
> the pool in active health probing, starts the admin HTTP server for metrics
> and
> health endpoints, and serves the Spark Connect gRPC surface through the proxy.
>
> gateway depends on all 14 other crates in the workspace, so it lands last of
> the
> code PRs and closes the dependency graph. With this PR the workspace members
> list
> is complete (15 crates) and `cargo build --workspace` produces a runnable
> `gateway` binary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
