[ https://issues.apache.org/jira/browse/LUCENE-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714039#action_12714039 ]
Mark Miller commented on LUCENE-1255: ------------------------------------- why should the first token have an increment of 1? I think the first token should always be 0. Increments are between tokens. and why do you want to know if the first token had an inc of 0 or 1? I think the -1 is a bug and it shows up elsewhere - eg spans,payloads, and most likely highlighting with the SpanHighlighter. > 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.16...@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-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org