You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hive.apache.org by na...@apache.org on 2013/01/17 18:49:16 UTC
svn commit: r1434811 - /hive/trunk/conf/hive-default.xml.template
Author: namit
Date: Thu Jan 17 17:49:16 2013
New Revision: 1434811
URL: http://svn.apache.org/viewvc?rev=1434811&view=rev
Log:
HIVE-3893 something wrong with the hive-default.xml
(jet cheng via namit)
Modified:
hive/trunk/conf/hive-default.xml.template
Modified: hive/trunk/conf/hive-default.xml.template
URL: http://svn.apache.org/viewvc/hive/trunk/conf/hive-default.xml.template?rev=1434811&r1=1434810&r2=1434811&view=diff
==============================================================================
--- hive/trunk/conf/hive-default.xml.template (original)
+++ hive/trunk/conf/hive-default.xml.template Thu Jan 17 17:49:16 2013
@@ -497,7 +497,7 @@
The merge is triggered if either of hive.merge.mapfiles or hive.merge.mapredfiles is set to true.
If the user has set hive.merge.mapfiles to true and hive.merge.mapredfiles to false, the idea was the
number of reducers are few, so the number of files anyway are small. However, with this optimization,
- we are increasing the number of files possibly by a big margin. So, we merge aggresively.
+ we are increasing the number of files possibly by a big margin. So, we merge aggresively.</description>
</property>
<property>
@@ -505,7 +505,7 @@
<value>false</value>
<description>Whether the version of hadoop which is running supports sub-directories for tables/partitions.
Many hive optimizations can be applied if the hadoop version supports sub-directories for
- tables/partitions. It was added by MAPREDUCE-1501
+ tables/partitions. It was added by MAPREDUCE-1501</description>
</property>
<property>
@@ -1130,7 +1130,7 @@
<value>200</value>
<description>
Determines if when the prefix of the key used for intermediate stats collection
- exceeds a certain length, a hash of the key is used instead. If the value < 0 then hashing
+ exceeds a certain length, a hash of the key is used instead. If the value < 0 then hashing
is never used, if the value >= 0 then hashing is used only when the key prefixes length
exceeds that value. The key prefix is defined as everything preceding the task ID in the key.
</description>