[
https://issues.apache.org/jira/browse/LUCENE-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14130818#comment-14130818
]
Uwe Schindler commented on LUCENE-5939:
---------------------------------------
By the way, this "displayversion" string is the reason why I was not so happy
that you removed it in 4.10. I renamed the constant to LUCENE_DISPLAY_VERSION
in my patch. You said, the information is useless (like svn rev number or user
that build or full version). It is in fact not. From that you can determine, if
an index was built using the "original lucene jars" or some (maybe modified)
private compiled versions. So I would really like to have that
LUCENE_DISPLAY_VERSION back (currently the constant LUCENE_VERSION that
contained this is deprecated). I would really like to write this version (e.g.
as display or full version string to the commit metadata). I had one customers
where i found out that they patched their lucene, causing corrumption. Based on
the CheckIndex output this was easy to detect. The display/full version
including rev no and user and appendix is in the JAR Manifest (which is good),
but no longer in index metadata!
> 4.10.1 cannot read 4.10 indexes
> -------------------------------
>
> Key: LUCENE-5939
> URL: https://issues.apache.org/jira/browse/LUCENE-5939
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Blocker
>
> Thank you mike for the smoketester addition. It failed because 4.10.1 was not
> verifying backwards compatibility against 4.10
> However, when i added the indexes (svn copied from branch-4x), the test fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
