[
https://issues.apache.org/jira/browse/HIVE-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898080#action_12898080
]
Joydeep Sen Sarma commented on HIVE-1530:
-----------------------------------------
ok - that makes sense. leave a hive-site.xml.sample and
hive-log4j.properties.example in the conf/. i agree with Ed's point about how
difficult it is to figure out hadoop config variables now and hadoop is worse
off for it. commands are nice - but having a template is better. it's easy to
clone an example file and append/modify the default description to add site
specific notes. and one can grep.
we could autogenerate the hive-site.xml.sample from config variable metadata in
the source code. that would keep us in sync with code.
> 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.
