Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <15668502.1203226868776.JavaMail.jira@brutus>
Date: Sat, 16 Feb 2008 21:41:08 -0800 (PST)
From: "Otis Gospodnetic (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-1179) AssertionError on creating doc
 containing field with empty string as field name
In-Reply-To: <26817516.1203087128618.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569639#action_12569639 ] 

Otis Gospodnetic commented on LUCENE-1179:
------------------------------------------

By the way, why are we allowing empty string field names in the first place?  Is there really a good use case for that?  If not, I wonder if we should try requiring a non-empty string field names in 3.0 and up.


> AssertionError on creating doc containing field with empty string as field name
> -------------------------------------------------------------------------------
>
>                 Key: LUCENE-1179
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1179
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Index
>    Affects Versions: 2.3
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 2.3.1, 2.4
>
>
> Spinoff from here:
>   http://www.gossamer-threads.com/lists/lucene/java-user/58496
> Pre-2.3 you were allowed to add Fields to a Document where the field name is the empty string.  In 2.3.0 it broke: you hit this during flush:
> {code}
> java.lang.AssertionError
>     at org.apache.lucene.index.TermInfosWriter.add(TermInfosWriter.java:143)
>     at org.apache.lucene.index.DocumentsWriter.appendPostings(DocumentsWriter.java:2290)
>     at org.apache.lucene.index.DocumentsWriter.writeSegment(DocumentsWriter.java:1985)
>     at org.apache.lucene.index.DocumentsWriter.flush(DocumentsWriter.java:539)
>     at org.apache.lucene.index.IndexWriter.doFlush(IndexWriter.java:2497)
>     at org.apache.lucene.index.IndexWriter.flush(IndexWriter.java:2397)
>     at org.apache.lucene.index.IndexWriter.closeInternal(IndexWriter.java:1204)
>     at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1178)
>     at org.apache.lucene.index.IndexWriter.close(IndexWriter.java:1153) 
> {code}
> The bug is just an over-aggressive assert statement.  I'll commit a fix shortly & port to 2.3 branch for 2.3.1 release.

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