[
https://issues.apache.org/jira/browse/HIVE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898040#action_12898040
]
Carl Steinbach commented on HIVE-1530:
--------------------------------------
@Ed: In my opinion the ideal solution is to get rid of the hive-default.xml
file entirely and rely on the default values that appear in HiveConf. We can
add a {{describe property xxxx}} command that prints out a description of the
property, and also add checks that protect the {{hive.*}} configuration
property namespace (i.e. you can't set a {{hive.*}} property unless it is
defined in HiveConf). Another advantage of this approach is that we don't have
to worry about hive-default.xml falling out of sync with HiveConf, e.g. a user
upgrades to a new version of Hive but continues to use an older copy of
hive-default.xml.
> 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.
