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

Brock Noland commented on HIVE-6037:
------------------------------------

bq. Then would hive-default.xml get used when hive-site.xml doesn't exist?

I believe the HiveConf class  would then use hive-default.xml to load defaults 
and descriptions.

bq. Wow, that's a labor of love. Let's not abandon it, 

Agreed, I think we should go forward with this patch

bq. let's use it as a one-time fix to get all the parameter descriptions into 
HiveConf. Then later we can figure out how to generate 
hive-default.xml.template from HiveConf for each new release. However there's a 
problem with the default values, since HiveConf sets them so those are the 
correct values.

AFAICT this patch moves the descriptions and defaults to 
hive-default.xml.template. I think the next step is generating hive-default.xml 
from the template. Then the HiveConf class uses hive-default.xml to load 
defaults and descriptions.

> Synchronize HiveConf with hive-default.xml.template and support show conf
> -------------------------------------------------------------------------
>
>                 Key: HIVE-6037
>                 URL: https://issues.apache.org/jira/browse/HIVE-6037
>             Project: Hive
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Navis
>            Priority: Minor
>         Attachments: HIVE-6037.1.patch.txt
>
>
> see HIVE-5879



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to