[
https://issues.apache.org/jira/browse/KNOX-3402?focusedWorklogId=1050316&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1050316
]
ASF GitHub Bot logged work on KNOX-3402:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Oct/26 14:52
Start Date: 26/Oct/26 14:52
Worklog Time Spent: 10m
Work Description: hanicz commented on PR #1335:
URL: https://github.com/apache/knox/pull/1335#issuecomment-6419082847
Closing due to inactivity, please reopen if you want to keep working on this
issue.
Issue Time Tracking
-------------------
Worklog Id: (was: 1050316)
Time Spent: 1h (was: 50m)
> 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: 1h
> 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
(v10.3.26#10030026)
