You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2017/04/04 08:15:41 UTC
[jira] [Resolved] (LUCENE-7756) Only record the major that was used
to create the index rather than the full version
[ https://issues.apache.org/jira/browse/LUCENE-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand resolved LUCENE-7756.
----------------------------------
Resolution: Fixed
Fix Version/s: master (7.0)
Thanks Mike for looking at this larg-ish patch!
> 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
> Fix For: master (7.0)
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org