[
https://issues.apache.org/jira/browse/LUCENE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12559748#action_12559748
]
Steven Rowe commented on LUCENE-1084:
-------------------------------------
An alternative to changing the default setting would be to not have a default -
make it a required parameter to the IndexWriter constructor. That way, there
is no silent loss (or gain) of content - the user must specify.
Maybe the type of this extra parameter could be an enumeration, along the lines
of BooleanClause.Occur, e.g. IndexWriter.FieldLength.LIMITED and
IndexWriter.FieldLength.UNLIMITED. LIMITED would set the max to the current
default, setMaxFieldLimit() would operate as it does currently, and UNLIMITED
would set the max to Integer.MAX_VALUE.
This solution would definitely be a backward-incompatible change, and would
have to wait for the 3.0 release.
> 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: Michael McCandless
> Fix For: 2.4
>
>
> 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]
