Hi Sue,
The thing that changes is that the indexing process will need more memory.
So if after changing this, and your system can run index init/update without
failing due to out-of-memory, then you are fine. So you can try using
max-int (-1), or find somewhere in-between.
*org.apache.lucene.index.IndexWriter <*0>*
public void *setMaxFieldLength*(int maxFieldLength)
The maximum number of terms 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. This setting refers to the number of running terms,
not to the number of different terms.
*Note:* this silently truncates large documents, excluding from the index
all terms 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 Integer.MAX_VALUE, then the only limit is
your memory, but you should anticipate an OutOfMemoryError.
By default, no more than 10,000 terms will be indexed for a field.
--
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries
On Tue, Dec 28, 2010 at 10:49 PM, Thornton, Susan M. (LARC-B702)[LITES] <
[email protected]> wrote:
> search.maxfieldlength
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
