hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Seth (JIRA)" <>
Subject [jira] [Commented] (HIVE-11358) LLAP: move LlapConfiguration into HiveConf and document the settings
Date Tue, 17 Nov 2015 19:30:11 GMT


Siddharth Seth commented on HIVE-11358:

bq. One question is, do we need a separate daemon config, or should we just use hive-site.xml
for everything?
Separate is better IMO, something other than hive-site.xml is less ambiguous. Also leaving
this as hive-site likely means a large (100+ k-v) config file for LLAP - of which only about
10 are required.

Given LLAP is a new component - we could get started with separating client and server configs
- along with the files.
llap.daemon.rpc.num.handlers (and a lot of other configs) <- useless in client configs
(hive-site on the client / hive-server)
llap.daemon.num.executors (and a few other configs) <- #threads for a daemon. Used by the
client to determine available slots when not using slider. The client config could be renamed.

IAC, that's beyond the scope of what this jira is doing. Using annotations to separate config
parameters to generate the public list of configurable fields would work.

I'll create a separate jira to separate llap server-side and client-side configs.

+1 for the patch.

> LLAP: move LlapConfiguration into HiveConf and document the settings
> --------------------------------------------------------------------
>                 Key: HIVE-11358
>                 URL:
>             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

View raw message