[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714577#action_12714577
]
Shai Erera commented on LUCENE-1542:
------------------------------------
I don't think there's a user-visible impact. This happens only if you set
posIncr=0 for the very first token. I guess it's not a common thing (if at
all), which is why we haven't heard of it?
I was worried though that if I have an index with -1s already encoded, and I
don't call setAllowMinus1Position, then some of the positions will be -1 and
some 0. And since it is deprecated, and will be removed in 3.0, I'll need to
reindex in 3.0.
But I agree that a bug fix should not be carried into the internal Lucene
processes. You should reindex.
> Lucene can incorrectly set the position of tokens that start a field with
> positonInc 0.
> ---------------------------------------------------------------------------------------
>
> Key: LUCENE-1542
> URL: https://issues.apache.org/jira/browse/LUCENE-1542
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Mark Miller
> Priority: Minor
> Fix For: 2.9
>
> Attachments: LUCENE-1542.patch, LUCENE-1542.patch, LUCENE-1542.patch
>
>
> More info in LUCENE-1465
--
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: [email protected]
For additional commands, e-mail: [email protected]
