turboFei commented on issue #7511: URL: https://github.com/apache/kyuubi/issues/7511#issuecomment-5446707299
Thanks, this is a useful clarification. The `SessionKey` plus `BackendMember.labels` model looks sufficient for USER-level affinity, so I agree that owner-label propagation should be handled in the gateway/discovery integration rather than added as a separate engine API.\n\nFor the remaining questions, my current choices are:\n\n1. Include `ReattachExecute` in the initial slice. Long-running and reconnectable executions are important for Spark Connect clients, and the gateway should preserve the RPC semantics from the beginning.\n3. Keep `kyuubi-spark-connect` as a top-level module. It is a server-side protocol frontend with its own dependency/profile boundary, and this keeps the existing `extensions/server` area focused on opt-in server extensions.\n4. Reuse the authenticated Kyuubi principal for downstream authorization. The bearer token should be resolved by the existing `AuthenticationProvider` chain; `UserContext.user_name` must not override that identity, and the resulting p rincipal should flow through the existing Ranger/HMS authorization path.\n\nI am also fine with the per-engine token via `--conf` and no token file for the first slice. Please start on the engine-side tasks, and bring any compatibility details for Spark 3.5/4.0 in the PR. -- 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]
