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 Sun, 20 Jan 2008 11:02:34 GMT


Michael McCandless commented on LUCENE-1084:

This patch looks great; thanks Steven!

This forces users to confront, up front, when creating IndexWriter,
whether they want to truncate the fields.

It deprecates all existing IndexWriter ctors, noting that in 3.0 they
will be removed, in favor of the version that adds the MaxFieldLength

We can commit this now, and then removed the deprecated APIs in 3.0.
I think with this change it's OK to leave the default truncation limit
at 10,000?

I think we can leave the with that current large limit?

I plan to commit in a day or two!

> 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: 3.0
>         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