Author: jnioche
Date: Thu Aug 12 18:23:29 2010
New Revision: 984897
URL: http://svn.apache.org/viewvc?rev=984897&view=rev
Log:
NUTCH-883 Removed unused parameters
Modified:
nutch/trunk/CHANGES.txt
nutch/trunk/conf/nutch-default.xml
Modified: nutch/trunk/CHANGES.txt
URL:
http://svn.apache.org/viewvc/nutch/trunk/CHANGES.txt?rev=984897&r1=984896&r2=984897&view=diff
==============================================================================
--- nutch/trunk/CHANGES.txt (original)
+++ nutch/trunk/CHANGES.txt Thu Aug 12 18:23:29 2010
@@ -2,6 +2,8 @@ Nutch Change Log
Release 2.0 - Current Development
+* NUTCH-883 Remove unused parameters from nutch-default.xml (jnioche)
+
* NUTCH-886 A .gitignore file for Nutch (dogacan)
* NUTCH-872 Change the default fetcher.parse to FALSE (ab).
Modified: nutch/trunk/conf/nutch-default.xml
URL:
http://svn.apache.org/viewvc/nutch/trunk/conf/nutch-default.xml?rev=984897&r1=984896&r2=984897&view=diff
==============================================================================
--- nutch/trunk/conf/nutch-default.xml (original)
+++ nutch/trunk/conf/nutch-default.xml Thu Aug 12 18:23:29 2010
@@ -551,14 +551,6 @@
updatedb will generate identical fetchlists.</description>
</property>
-<property>
- <name>generate.max.per.host</name>
- <value>-1</value>
- <description>(Deprecated). Use generate.max.count and generate.count.mode
instead.
- The maximum number of urls per host in a single
- fetchlist. -1 if unlimited.</description>
-</property>
-
<!-- urlpartitioner properties -->
<property>
<name>partition.url.mode</name>
@@ -671,86 +663,6 @@
</description>
</property>
-<!-- indexer properties -->
-
-<property>
- <name>indexer.score.power</name>
- <value>0.5</value>
- <description>Determines the power of link analyis scores. Each
- pages's boost is set to <i>score<sup>scorePower</sup></i> where
- <i>score</i> is its link analysis score and <i>scorePower</i> is the
- value of this parameter. This is compiled into indexes, so, when
- this is changed, pages must be re-indexed for it to take
- effect.</description>
-</property>
-
-<property>
- <name>indexer.max.title.length</name>
- <value>100</value>
- <description>The maximum number of characters of a title that are indexed.
- </description>
-</property>
-
-<property>
- <name>indexer.max.tokens</name>
- <value>10000</value>
- <description>
- The maximum number of tokens that will be indexed for a single field
- in a document. This limits the amount of memory required for
- indexing, so that collections with very large files will not crash
- the indexing process by running out of memory.
-
- Note that this effectively truncates large documents, excluding
- from the index tokens that occur further in the document. If you
- know your source documents are large, be sure to set this value
- high enough to accomodate the expected size. If you set it to
- -1, then the only limit is your memory, but you should anticipate
- an OutOfMemoryError.
- </description>
-</property>
-
-<property>
- <name>indexer.mergeFactor</name>
- <value>50</value>
- <description>The factor that determines the frequency of Lucene segment
- merges. This must not be less than 2, higher values increase indexing
- speed but lead to increased RAM usage, and increase the number of
- open file handles (which may lead to "Too many open files" errors).
- NOTE: the "segments" here have nothing to do with Nutch segments, they
- are a low-level data unit used by Lucene.
- </description>
-</property>
-
-<property>
- <name>indexer.minMergeDocs</name>
- <value>50</value>
- <description>This number determines the minimum number of Lucene
- Documents buffered in memory between Lucene segment merges. Larger
- values increase indexing speed and increase RAM usage.
- </description>
-</property>
-
-<property>
- <name>indexer.maxMergeDocs</name>
- <value>2147483647</value>
- <description>This number determines the maximum number of Lucene
- Documents to be merged into a new Lucene segment. Larger values
- increase batch indexing speed and reduce the number of Lucene segments,
- which reduces the number of open file handles; however, this also
- decreases incremental indexing performance.
- </description>
-</property>
-
-<property>
- <name>indexer.termIndexInterval</name>
- <value>128</value>
- <description>Determines the fraction of terms which Lucene keeps in
- RAM when searching, to facilitate random-access. Smaller values use
- more memory but make searches somewhat faster. Larger values use
- less memory but make searches somewhat slower.
- </description>
-</property>
-
<!-- indexingfilter plugin properties -->
<property>
@@ -769,6 +681,25 @@
</description>
</property>
+<property>
+ <name>indexer.score.power</name>
+ <value>0.5</value>
+ <description>Used by the OPIC plugin. Determines the power of link analyis
scores.
+ Each pages's boost is set to <i>score<sup>scorePower</sup></i> where
+ <i>score</i> is its link analysis score and <i>scorePower</i> is the
+ value of this parameter. This is compiled into indexes, so, when
+ this is changed, pages must be re-indexed for it to take
+ effect.</description>
+</property>
+
+<property>
+ <name>indexer.max.title.length</name>
+ <value>100</value>
+ <description>The maximum number of characters of a title that are indexed.
+ Used by index-basic.
+ </description>
+</property>
+
<!-- URL normalizer properties -->
<property>
