[
https://issues.apache.org/jira/browse/LUCENE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128758#comment-14128758
]
Robert Muir commented on LUCENE-5863:
-------------------------------------
They are removed. For example all 3.x indexes are no longer supported in 5.x.
But if you look in 5.x, have all the indexes been moved to the "unsupported
test"? Nope, some are missing. So we currently have no idea what behavior a
user will get in that situation.
Bottom line, our back compat is complicated enough that I really think this is
needed. Its not like its slow or anything, so i dont understand the objection
to it: it just reads a directory listing?
I really don't want a release going out, if such a release has broken backwards
compatibility. Mike's checker gives me confidence that at least the minimal
bases are covered.
> Generate backwards compatibility indexes for all 4.x releases
> -------------------------------------------------------------
>
> Key: LUCENE-5863
> URL: https://issues.apache.org/jira/browse/LUCENE-5863
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Attachments: testTheBWCTester.py
>
>
> Currently the versioning here is a total mess, and its inconsistent across
> bugfix releases.
> We should just generate back compat indexes for every release: regardless of
> whether the index format changed, even for bugfix releases. This ensures at
> least we try to test that the back compat is working.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
