[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lucene-dev
Subject:    [jira] Reopened: (LUCENE-1255) CheckIndex should allow term
From:       "Michael Busch (JIRA)" <jira () apache ! org>
Date:       2008-04-28 22:11:55
Message-ID: 529382017.1209420715686.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/LUCENE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Michael Busch reopened LUCENE-1255:
-----------------------------------


> CheckIndex should allow term position = -1
> ------------------------------------------
> 
> Key: LUCENE-1255
> URL: https://issues.apache.org/jira/browse/LUCENE-1255
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.4
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Priority: Minor
> Fix For: 2.3.2, 2.4
> 
> Attachments: LUCENE-1255.patch, LUCENE-1255.take2.patch
> 
> 
> Spinoff from this discussion:
> http://mail-archives.apache.org/mod_mbox/lucene-java-user/200803.mbox/%3CPine.LNX.4.62.0803292323350.16762@radix.cryptio.net%3E
>  Right now CheckIndex claims the index is corrupt if you index a Token with -1 \
> position, which happens if your first token has positionIncrementGap set to 0. But, \
> as far as I can tell, Lucene doesn't "mind" when this happens. So I plan to fix \
> CheckIndex to allow this case.  I'll backport to 2.3.2 as well. LUCENE-1253 is one \
> example where Lucene's core analyzers could do this.

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


[prev in list] [next in list] [prev in thread] [next in thread]