[
https://issues.apache.org/jira/browse/LUCENE-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130138#comment-14130138
]
Tim Smith commented on LUCENE-5940:
-----------------------------------
5.0 should not be saddled with supporting 3.x index. 100% agree there
however, 5.0 should ideally continue to support 4.0-4.99 indexes (at least from
the codec/index reading perspective)
the best place to handle backwards compat is in the core of lucene.
otherwise, you are just going to have uses all over the place doing their own
interpretation of "backwards compat", getting it wrong, broken, etc. and will
subsequently result in lots of irate user filing tickets.
if you only support the last minor version from the previous release, it makes
it difficult for everyone who was not at that exact minor release.
also, to uwe's point the "indexupgrade" tool is an offline process. also, in my
situation, i would need custom packaging of that tool in order to provide ease
of use/proper codec usage, etc. vs just fire up index on 5.0 and forceMerge.
the custom packaging would also require including an "old" version of lucene in
my project that would be packaged separately, and would just be a nightmare to
maintain.
alternatively, i would just grab the source for all removed 4.x codecs i need
and pull them into my project (this is not ideal since they are no longer
maintained by lucene devs and may have dependency issues that would require
porting)
> 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
