[
https://issues.apache.org/jira/browse/LUCENE-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714400#action_12714400
]
Shai Erera commented on LUCENE-1542:
------------------------------------
So Mike, just for clarification - let's say I have an index with -1 encoded for
positions, already. I then upgrade to 2.9 and realize I should set this on
IndexWriter, so in fact more -1 positions will be encoded.
My question is - when will those -1 positions be fixed? I think this breaks
back-compat since it changes the indexed data, and should be handled just like
any other indexed data/format changes - i.e., last until 4.0. In the meantime,
we can make sure that when segments are merged, or the index is optimized, or
whatever else we do to support those back-compat issues, we fix those
encodings, so that hopefully by 4.0 my indexes don't contain the -1s anymore
(if they do, then I'm screwed and can choose between not upgrading to 4.0, or
rebuild them).
If I'm right, then you don't need this deprecated method, and make the changes
under the covers?
If I'm wrong, and our back-compat policy only covers index format changes, then
I will already need to rebuild my indexes, so why wait until 3.0? Basically
this is one of the cases that were discussed recently on the back-compat policy
thread - a change to indexed data. One that we did not agree on (I vaguely
remember we said it should be handled like index format changes, but I may be
wrong).
> 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]
