You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/02/07 06:16:00 UTC

[jira] [Commented] (SPARK-37735) Add appId interface to KubernetesConf

    [ https://issues.apache.org/jira/browse/SPARK-37735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17487888#comment-17487888 ] 

Apache Spark commented on SPARK-37735:
--------------------------------------

User 'martin-g' has created a pull request for this issue:
https://github.com/apache/spark/pull/35413

> Add appId interface to KubernetesConf
> -------------------------------------
>
>                 Key: SPARK-37735
>                 URL: https://issues.apache.org/jira/browse/SPARK-37735
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Kubernetes
>    Affects Versions: 3.3.0
>            Reporter: Yikun Jiang
>            Assignee: Yikun Jiang
>            Priority: Major
>             Fix For: 3.3.0
>
>
> The appId now can be only access in KuberntesDriverConf and KubernetesExecutorConf, but can't be accesss in KubernetesConf.
>  
> Some user featurestep are using KubernetesConf as init constructor parameter in order to share the featurestep between driver and executor. So, we'd better add appId to KubernetesConf to help such featurestep access appId.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org