lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Resolved: (LUCENE-1330) 0 position increment not properly supported for the first token
Date Mon, 22 Sep 2008 17:48:44 GMT


Michael McCandless resolved LUCENE-1330.

    Resolution: Duplicate

Dup of LUCENE-1255.

> 0 position increment not properly supported for the first token
> ---------------------------------------------------------------
>                 Key: LUCENE-1330
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: Javadocs, Store
>            Reporter: Moti Nisenson
> Setting a position increment of 0 for the first token in a field results in its "absolute
position" (as well as increment) being read back later as Integer.MIN_VALUE.
> This is a result of how the information gets written out in DocumentsWriter: position
should not be updated using += t.getPositionIncrement() - 1; and then always ++'ed in addPosition.
It would be much simpler just to update it using t.getPositionIncrement().
> While this is fairly easy to fix in DocumentsWriter, one could just update the documentation
for Token.setPositionIncrement() to indicate that for indexing purposes the first Token in
a field must have a positive position increment.

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