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

Posted to issues@livy.apache.org by "Alex Bozarth (JIRA)" <ji...@apache.org> on 2017/11/28 20:49:00 UTC

[jira] [Resolved] (LIVY-422) Change livy.spark.deploy-mode to livy.spark.deployMode in livy.conf.template

     [ https://issues.apache.org/jira/browse/LIVY-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Bozarth resolved LIVY-422.
-------------------------------
    Resolution: Not A Problem

We updated our config naming in https://github.com/apache/incubator-livy/commit/221aa9cf8f33b48fd9c792f67c61b78708bfae99 which was included in 0.4
So this isn't an issue, just a difference between 0.3 and 0.4, sorry for any confusion or inconvenience

> Change livy.spark.deploy-mode to livy.spark.deployMode in livy.conf.template
> ----------------------------------------------------------------------------
>
>                 Key: LIVY-422
>                 URL: https://issues.apache.org/jira/browse/LIVY-422
>             Project: Livy
>          Issue Type: Bug
>            Reporter: Lucas Partridge
>            Priority: Minor
>
> Shouldn't livy.spark.deploy-mode at https://github.com/apache/incubator-livy/blob/master/conf/livy.conf.template#L36 be livy.spark.deployMode? Because the latter is what's used in https://github.com/cloudera/livy/commit/7448c7c#diff-18b55407feae186248ae4f664d0fe47dR17



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)