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

   ### What changes were proposed in this pull request?
   
   This is the first of a series of small, bottom-up PRs importing the Spark
   Connect Gateway reference implementation (tracked in the do-not-merge 
reference
   PR #1). It introduces the Cargo workspace:
   
   - Root `Cargo.toml` with the full `[workspace.package]` and
     `[workspace.dependencies]` tables. `members` lists only `crates/genproto` 
for
     now; subsequent PRs append one or more crates.
   - `Cargo.lock` (tracked — this project ships a binary), 
`rust-toolchain.toml`.
   - The vendored `spark.connect.*` protos under `proto/spark/connect/` — a
     read-only mirror of the corresponding files in `apache/spark`.
   - The `scg-genproto` crate, whose `build.rs` generates tonic bindings from 
the
     protos at build time via `tonic-prost-build`.
   
   Each PR in this series keeps `main` green under the full CI matrix
   (fmt / clippy --all-targets / build / test --workspace).
   
   ### Why are the changes needed?
   
   Implements the reference gateway from the approved SPIP (SPARK-58455), 
imported
   into the `apache/spark-connect-gateway` subproject repo 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.
   
   ### 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