lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-1084) increase default maxFieldLength?
Date Thu, 07 Feb 2008 15:10:08 GMT


Michael McCandless commented on LUCENE-1084:

Yeah, the intention here was that you specify LIMITED or UNLIMITED enum parameter on creating
the IW, and then change the actual limit using setMaxFieldLength.

But I agree it'd be cleaner if you could actually just set the limit (once) on construction.

I think if we stopped subclassing from Parameter (we don't really need Serializable here?),
and made the ctor public, then you could pass in "new MaxFieldLength(100000)" to make your
own limit?

> increase default maxFieldLength?
> --------------------------------
>                 Key: LUCENE-1084
>                 URL:
>             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:
For additional commands, e-mail:

View raw message