[
https://issues.apache.org/jira/browse/HIVE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898030#action_12898030
]
Edward Capriolo commented on HIVE-1530:
---------------------------------------
I like the default xml. Hive has many undocumented options, new ones are being
added often. Are end users going to know which jar the default.xml are in?
Users want to extracting a jar just to get the conf out of it to read the
description of the setting.
As for what hadoop does...I personally find it annoying to have navigate to
hadoop/src/mapred/mapred-default.xml or to hadoop/src/hdfs/hdfs-default.xml to
figure out what options I have for settings. So i do not really thing we should
just do it to be like hadoop it it makes peoples life harder.
If anything please keep it as hive-site.xml.sample.
> Include hive-default.xml and hive-log4j.properties in hive-common JAR
> ---------------------------------------------------------------------
>
> Key: HIVE-1530
> URL: https://issues.apache.org/jira/browse/HIVE-1530
> Project: Hadoop Hive
> Issue Type: Improvement
> Components: Configuration
> Reporter: Carl Steinbach
>
> hive-common-*.jar should include hive-default.xml and hive-log4j.properties,
> and similarly hive-exec-*.jar should include hive-exec-log4j.properties. The
> hive-default.xml file that currently sits in the conf/ directory should be
> removed.
> Motivations for this change:
> * We explicitly tell users that they should never modify hive-default.xml yet
> give them the opportunity to do so by placing the file in the conf dir.
> * Many users are familiar with the Hadoop configuration mechanism that does
> not require *-default.xml files to be present in the HADOOP_CONF_DIR, and
> assume that the same is true for HIVE_CONF_DIR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
