[
https://issues.apache.org/jira/browse/LUCENE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954749#comment-15954749
]
ASF subversion and git services commented on LUCENE-7756:
---------------------------------------------------------
Commit 23b002a0fdf2f6025f1eb026c0afca247fb21ed0 in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=23b002a ]
LUCENE-7756: Only record the major Lucene version that created the index, and
record the minimum Lucene version that contributed to segments.
> Only record the major that was used to create the index rather than the full
> version
> ------------------------------------------------------------------------------------
>
> Key: LUCENE-7756
> URL: https://issues.apache.org/jira/browse/LUCENE-7756
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7756.patch, LUCENE-7756.patch, LUCENE-7756.patch
>
>
> LUCENE-7703 added information about the Lucene version that was used to
> create the index to the segment infos. But since there is a single creation
> version, it means we need to reject calls to addIndexes that can mix indices
> that have different creation versions, which might be seen as an important
> regression by some users. So I have been thinking about only recording the
> major version that was used to create the index, which is still very valuable
> information and would allow us to accept calls to addIndexes when all merged
> indices have the same major version. This looks like a better trade-off to me.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
