You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Larry McCay (Jira)" <ji...@apache.org> on 2026/08/21 21:36:00 UTC
[jira] [Assigned] (KNOX-3402) gRPC gateway support
[ https://issues.apache.org/jira/browse/KNOX-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Larry McCay reassigned KNOX-3402:
---------------------------------
Assignee: Alex Cruise
> gRPC gateway support
> --------------------
>
> Key: KNOX-3402
> URL: https://issues.apache.org/jira/browse/KNOX-3402
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Reporter: Alex Cruise
> Assignee: Alex Cruise
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This started out intended only to support [Spark Connect|https://spark.apache.org/spark-connect/], which is a gRPC-native protocol for Apache Spark that allows end users to interact with Spark clusters and submit jobs through a principled API, from languages that aren't necessarily Python, Scala or SQL. Spark Connect itself explicitly disclaims any support for authentication or authorization; rather Spark suggests installing one's own gRPC gateway between client and server if such functionality is needed. Knox could be that gateway!
> The original intent of this project was only to support Spark Connect rather than arbitrary gRPC workloads, but the Spark Connect-specific parts turned out to be very small, and making it fully generic required very little additional code. Knox doesn't _exactly_ support proxying arbitrary REST traffic right now, but it makes it pretty easy.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)