[
https://issues.apache.org/jira/browse/LUCENE-8264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447672#comment-16447672
]
Adrien Grand commented on LUCENE-8264:
--------------------------------------
Lucene only supports reading indices generated by versions N or N-1, so I don't
think we should help users go into unsupported territory by attempting
5x->6x->7x upgrades? For the record, it might "work" in that very particular
case because we didn't change anything on top of the codec API between 5x and
6x (I think?), but a 6x->7x->8x would be problematic since 7x started rejecting
corrupt offsets and changed the encoding of norms, so attempting a 6x->7x->8x
upgrade this way could propagate corrupt offsets to 8x and would corrupt norms.
To avoid this trap we started recording the creation version in LUCENE-7703 and
LUCENE-7756, and then failed opening 6x (or less) indices with 8x in
LUCENE-7837.
> Allow an option to rewrite all segments
> ---------------------------------------
>
> Key: LUCENE-8264
> URL: https://issues.apache.org/jira/browse/LUCENE-8264
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Priority: Major
>
> For the background, see SOLR-12259.
> There are several use-cases that would be much easier, especially during
> upgrades, if we could specify that all segments get rewritten.
> One example: Upgrading 5x->6x->7x. When segments are merged, they're
> rewritten into the current format. However, there's no guarantee that a
> particular segment _ever_ gets merged so the 6x-7x upgrade won't necessarily
> be successful.
> How many merge policies support this is an open question. I propose to start
> with TMP and raise other JIRAs as necessary for other merge policies.
> So far the usual response has been "re-index from scratch", but that's
> increasingly difficult as systems get larger.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
