[
https://issues.apache.org/jira/browse/LUCENE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Rowe updated LUCENE-1084:
--------------------------------
Attachment: LUCENE-1084.part2.take2.patch
The javadoc description of the MaxFieldLength parameter (mfl) in the
IndexWriter constructors is now "whether or not to limit field lengths".
This should probably be rewritten in light of the change allowing user
specification of values other than LIMITED or UNLIMITED. How's this?:
{code}
/** ...
* @param mfl Maximum field length: LIMITED, UNLIMITED, or user-specified
* via the MaxFieldLength constructor.
* ...
*/
{code}
Attaching part2.take2 patch including this javadoc change and the
MaxFieldLength extension and constructor changes.
> increase default maxFieldLength?
> --------------------------------
>
> Key: LUCENE-1084
> URL: https://issues.apache.org/jira/browse/LUCENE-1084
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.2
> Reporter: Daniel Naber
> Assignee: Steven Rowe
> Fix For: 2.4
>
> Attachments: LUCENE-1084.part2.patch, LUCENE-1084.part2.take2.patch,
> LUCENE-1084.patch
>
>
> To my understanding, Lucene 2.3 will easily index large documents. So
> shouldn't we get rid of the 10,000 default limit for the field length? 10,000
> isn't that much and as Lucene doesn't have any error logging by default, this
> is a common problem for users that is difficult to debug if you don't know
> where to look.
> A better new default might be Integer.MAX_VALUE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
