[
https://issues.apache.org/jira/browse/LUCENE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566600#action_12566600
]
Grant Ingersoll commented on LUCENE-1084:
-----------------------------------------
Sorry for the lateness on this, was just looking at another patch that had the
deprecated constructor and was going to replace it...
How, exactly, is one supposed to specify an alternate value for the
MaxFieldLength in the constructor when using the IndexWriter.MaxFieldLength
constructor when it is private and not extendable? Or is it that I pass in a
LIMITED or UNLIMITED and then immediately go call
indexWriter.setMaxFieldLength()? That doesn't make sense to me from a user's
point of view of trying to understand how to set the maxFieldLength, so I feel
like I must be missing something.
> 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
>
> Attachments: 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]
