[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130218#comment-14130218
]
Tim Smith commented on LUCENE-5940:
-----------------------------------
the problem with the upgrade tool approach is that it doesn't scale to clusters
with large numbers of indexes.
for instance, a cluster that has 50 indexes spread across a bunch of machines.
this is now an involved manual task put in the hands of system administrators
who don't really know whats going on under the hood.
thats just asking for trouble
it seems like the whole power of codecs is that you can avoid all this and
allow for seamless transitions by having read only codecs for previous index
formats.
are there technical issues here i'm unaware of beyond creating and maintaining
the backwards compat tests?
something outside of the codec mechanism that causes problems?
if not, just dump the read only codecs for old versions in an contrib module
and let people upgrade at their leisure (and let the community find/fix bugs as
they are encountered)
> 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]
