You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@livy.apache.org by "Alexey Romanenko (JIRA)" <ji...@apache.org> on 2018/08/13 09:14:00 UTC
[jira] [Resolved] (LIVY-450) Override config options by environment
variables.
[ https://issues.apache.org/jira/browse/LIVY-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Romanenko resolved LIVY-450.
-----------------------------------
Resolution: Won't Do
After discussion on github it was agreed to not continue with this approach.
> Override config options by environment variables.
> -------------------------------------------------
>
> Key: LIVY-450
> URL: https://issues.apache.org/jira/browse/LIVY-450
> Project: Livy
> Issue Type: Improvement
> Reporter: Alexey Romanenko
> Priority: Major
>
> Add a possibility to override all config options by environment variables.
> For example:
> {{LIVY_SPARK_MASTER}} automatically overrides {{livy.spark.master}} and {{LIVY_SPARK_DEPLOY_MODE}} overrides {{livy.spark.deploy-mode}}.
> It can be quite useful to use the same Livy image in different modes (local and cluster).
> Any pros/cons for or against that?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)