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

Posted to issues@livy.apache.org by "Akshat Bordia (Jira)" <ji...@apache.org> on 2019/12/27 13:02:00 UTC

[jira] [Commented] (LIVY-661) POST /sessions API - Conf parameters

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

Akshat Bordia commented on LIVY-661:
------------------------------------

[~asethia7478]  This looks like to be the designed behaviour as per the code. Conf passed via Livy API takes the highest precedence. Can you please tell which other conf properties are appending with default conf?

> POST /sessions API - Conf parameters
> ------------------------------------
>
>                 Key: LIVY-661
>                 URL: https://issues.apache.org/jira/browse/LIVY-661
>             Project: Livy
>          Issue Type: Bug
>          Components: API
>            Reporter: Arun Sethia
>            Priority: Critical
>
> The Livy POST /sessions API  allows to pass conf (Spark configuration properties). When we pass spark.driver.extraJavaOptions as conf, It overrides the cluster default spark.driver.extraJavaOptions, Ideally it should append with default conf like it is done for other conf values.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)