Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 73451 invoked from network); 7 Feb 2008 18:39:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 18:39:34 -0000 Received: (qmail 9565 invoked by uid 500); 7 Feb 2008 18:39:27 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 8919 invoked by uid 500); 7 Feb 2008 18:39:25 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 8908 invoked by uid 99); 7 Feb 2008 18:39:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 10:39:25 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 18:39:17 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 00DF171407A for ; Thu, 7 Feb 2008 10:39:10 -0800 (PST) Message-ID: <4954388.1202409549989.JavaMail.jira@brutus> Date: Thu, 7 Feb 2008 10:39:09 -0800 (PST) From: "Steven Rowe (JIRA)" To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-1084) increase default maxFieldLength? In-Reply-To: <25336561.1197067003215.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/LUCENE-1084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566728#action_12566728 ] Steven Rowe commented on LUCENE-1084: ------------------------------------- Mike, I see you added a test for the user-specified max field length - cool. It made me think of the IndexHTML.java usage, which should probably be changed to conform to the new style: {code} writer = new IndexWriter(index, new StandardAnalyzer(), create, IndexWriter.MaxFieldLength.LIMITED); writer.setMaxFieldLength(1000000); {code} should be: {code} writer = new IndexWriter(index, new StandardAnalyzer(), create, new IndexWriter.MaxFieldLength(1000000)); {code} Hmm, now that I look, I can see several other new IndexWriter() / setMaxFieldLength() sequences that should be changed ... I'll submit a patch shortly. > 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: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org