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

Posted to issues@livy.apache.org by "Jeff Zhang (JIRA)" <ji...@apache.org> on 2018/04/01 03:40:00 UTC

[jira] [Commented] (LIVY-450) Override config options by environment variables.

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

Jeff Zhang commented on LIVY-450:
---------------------------------

Sorry for late response, Thanks for the detail explanation [~ryanskraba] [~aromanenko] The docker scenario make sense to me, thoughts ? \cc [~jerryshao]

> 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)