[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130131#comment-14130131
]
Uwe Schindler commented on LUCENE-5940:
---------------------------------------
bq. however, if product X released with lucene 4.88 and the last minor version
in 4.x line was 4.99, then the upgrade process to get to a lucene 5.0 index is
now convoluted and will require creation of custom offline tools to provide an
upgrade path. the current policy does not have these issues since all that i
would need to do is fire up the next version, do a forceMerge, and everything
is up to date on latest codecs. (no offline processes required, search can
continue to work during upgrade)
We have a tool that does this without forceMerge. It just upgrades those
segments that need upgrade and writes a new commit point. It is called
IndexUpgrader and has a main method.
My idea would be to privtde that tool, including all stuff as a self-executing
JAR file, so you just need: {{java -jar lucene-indexupgrader-4.10.0.jar
indexdir}} (basically it is already like that, but you need to build classpath
and command line manually).
> change index backwards compatibility policy.
> --------------------------------------------
>
> Key: LUCENE-5940
> URL: https://issues.apache.org/jira/browse/LUCENE-5940
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> Currently, our index backwards compatibility is unmanageable. The length of
> time in which we must support old indexes is simply too long.
> The index back compat works like this: everyone wants it, but there are
> frequently bugs, and when push comes to shove, its not a very sexy thing to
> work on/fix, so its hard to get any help.
> Currently our back compat "promise" is just a broken promise, because we
> cannot actually guarantee it for these reasons.
> I propose we scale back the length of time for which we must support old
> indexes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
