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

   ### What changes were proposed in this pull request?
   
   This PR imports the full Spark Connect Gateway reference implementation as a
   single squashed commit.
   
   **This PR is intentionally too large to review and is NOT meant to be 
merged.**
   It exists only as the reference / target end-state so reviewers can see the 
whole
   picture. The implementation will be split into smaller, self-contained,
   reviewable PRs that land one at a time (in dependency order, bottom-up). 
After
   each small PR merges, this reference PR is rebased and shrinks until 
everything
   is imported and it can be closed.
   
   The import includes: the Cargo workspace (15 crates under `crates/`), the 
Helm
   chart (`deploy/helm/scg/`), e2e examples (`deploy/examples/`), docs 
(`docs/`),
   the vendored `spark.connect.*` protos (`proto/`), and the full README. Every
   imported source file carries the Apache license header; the vendored protos
   retain their upstream ASF headers.
   
   ### Why are the changes needed?
   
   Implements the reference gateway from the approved SPIP (SPARK-58455), 
moving it
   into the `apache/spark-connect-gateway` subproject repo.
   
   ### Does this PR introduce _any_ user-facing change?
   
   No.
   
   ### How was this patch tested?
   
   `cargo check --workspace --all-targets` and `cargo fmt --check` pass locally;
   `helm lint` passes on the chart. Per-crate tests come in with the split PRs.
   
   ### 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