[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130103#comment-14130103
]
Ryan Ernst commented on LUCENE-5940:
------------------------------------
Big +1. Our current policy has us supporting indexes 4+ years old, and given
how long 4x is lasting, that will just keep stretching. Obviously there needs
to be an upgrade path, but I don't think it needs to be so easy for someone
that hasn't upgraded in 4 years.
My concrete proposal is supporting the current major release, plus the last
minor release of the previous major release. That should provide an upgrade
path by first updating to the last minor release of the major release you are
using, followed by the lastest of the next major release. Given the 4.x
architecture with codecs, this should be much easier than it has been to
maintain 3x index formats.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
