[
https://issues.apache.org/jira/browse/LUCENE-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076168#comment-14076168
]
Robert Muir commented on LUCENE-5850:
-------------------------------------
The real bug here is not what simon describes... (although I think its
confusing, and its extra confusing there are "two versions").
It is not that 4.8.1 is good, actually 4.8.1 is the buggy one. Segments with
4.8.1 say they were written with "4.8", which is broken.
Furthermore, code like Lucene45DocValuesProducer doing stuff like the below is
also broken:
{code}
Version.parseLeniently(state.segmentInfo.getVersion());
{code}
The main problem is caused by the overengineering of this shit: two different
version values, one of which is driven by a system property, and other
confusion. Because of this its also not tested. I realize this system property
shit is supposed to be there to support "strange" things like custom builds and
maven snapshots, but its gotta die. Sorry, its broken for actual lucene
releases!
> Constants#LUCENE_MAIN_VERSION can have broken values
> -----------------------------------------------------
>
> Key: LUCENE-5850
> URL: https://issues.apache.org/jira/browse/LUCENE-5850
> Project: Lucene - Core
> Issue Type: Bug
> Components: general/build
> Affects Versions: 4.3.1, 4.5.1
> Reporter: Simon Willnauer
> Fix For: 5.0, 4.10
>
>
> Constants#LUCENE_MAIN_VERSION is set to the Lucene Main version and should
> not contain minor versions. Well this is at least what I thought and to my
> knowledge what the comments say too. Yet in for instance 4.3.1 and 4.5.1 we
> broke this such that the version from SegmentsInfo can not be parsed with
> Version#parseLeniently. IMO we should really add an assertion that this
> constant doesn't throw an error and / or make the smoketester catch this. to
> me this is actually a index BWC break. Note that 4.8.1 doesn't have this
> problem...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
