[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131951#comment-14131951
]
Tim Smith commented on LUCENE-5940:
-----------------------------------
i fully understand the reasons for wanting to change the policy here. i
absolutely hate maintaining backwards compat myself. its just a nightmare and
leaves lots of rotting code laying around waiting to wreak havoc and makes it
dicey to add new functionality. i'm fully on board with that sentiment
but, i have to support it, and do so in a seamless online manner that is not
prone to user error.
i also get the feeling a lot of the lucene devs in general don't think "full
reindexing" is an issue and can just be done at any point with minimal cost
(just a vibe i've picked up). my experience is that this can be a many months
long process (slow sources). this seems to influence support for backwards
compatibility, as well as support for changing configuration/schema options,
for existing fields, etc
by all means, create a good upgrade tool people can use. however, it won't be
useful for me and i will need to find a different solution (which will likely
result in slowing my adoption of 5.0 when it is released)
i am in no way advocating that 5.0 should support reading 3.x indexes.
again, i'm just adding my perspective here so informed people can make a
decision based on all points of view
if the policy changes, i will just have to adapt as necessary
> 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]
