You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/08/06 06:55:00 UTC
[jira] [Commented] (SPARK-28627) properties file via SPARK_CONF_DIR
and --properties-file prevents definition of own properties via secrets/own
mounts
[ https://issues.apache.org/jira/browse/SPARK-28627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900695#comment-16900695 ]
Hyukjin Kwon commented on SPARK-28627:
--------------------------------------
[~rolandjohann], looks it's better to ask in mailing list before filing it as an issue here
> properties file via SPARK_CONF_DIR and --properties-file prevents definition of own properties via secrets/own mounts
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-28627
> URL: https://issues.apache.org/jira/browse/SPARK-28627
> Project: Spark
> Issue Type: Bug
> Components: Kubernetes
> Affects Versions: 2.4.3
> Reporter: Roland Johann
> Priority: Major
>
> K8S resource manager dumps the config map to /opt/spark/conf/spark-defaults.conf and passes it to spark submit twice:
> * via env var SPARK_CONF_DIR
> * argument --properties-file
> This prevents definition if user defined properties, such as from secrets - currently it seems to be the only possibility to define spark config properties from secrets but is locked currently.
> Is this implementation intent? If yes, what are the reasons behind this decision?
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org