[jira] [Commented] (HIVE-11358) LLAP: move LlapConfiguration into HiveConf and document the settings

["Siddharth Seth (JIRA)" <ji...@apache.org>]

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

Siddharth Seth commented on HIVE-11358:
---------------------------------------

Is there a way to group the LLAP variables separately in HiveConf ? The mechanics for validation and parameter access offered by HiveConf are definitely useful. At the same time, it would be useful to separate out LLAP parameters (and within that separate out client / daemon config properties at a later point).
llap-daemon-site still exists - but there will be confusion about what goes into this, vs what goes into hive-site.xml. Does the daemon require a hive-site while starting up ?

With YARN and HDFS - a perpetual source of confusion has been separation of client vs server configs. This ends up with servers and clients using the same config files (sane path), and the same property names. As a result - knowing whether a parameter change affects the server / client is confusing, also where a change is required is confusing. Separating the configs within HiveConf would be useful for something like this.

Functionally, the patch looks good.

> LLAP: move LlapConfiguration into HiveConf and document the settings
> --------------------------------------------------------------------
>
>                 Key: HIVE-11358
>                 URL: https://issues.apache.org/jira/browse/HIVE-11358
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>         Attachments: HIVE-11358.01.patch, HIVE-11358.patch
>
>
> Hive uses HiveConf for configuration. LlapConfiguration should be replaced with parameters in HiveConf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)