[
https://issues.apache.org/jira/browse/LUCENE-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888099#comment-15888099
]
ASF subversion and git services commented on LUCENE-7703:
---------------------------------------------------------
Commit d9c0f2599d934766549b2566d7c0dd159c3af5c8 in lucene-solr's branch
refs/heads/master from [~jpountz]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d9c0f25 ]
LUCENE-7703: Record the index creation version.
> Record the version that was used at index creation time
> -------------------------------------------------------
>
> Key: LUCENE-7703
> URL: https://issues.apache.org/jira/browse/LUCENE-7703
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-7703.patch
>
>
> SegmentInfos already records the version that was used to write a commit and
> the version that was used to write the oldest segment in the index. In
> addition to those, I think it could be useful to record the Lucene version
> that was used to create the index. I think it could help with:
> - Debugging: there are things that change based on Lucene versions, for
> instance we will reject broken offsets in term vectors as of 7.0. Knowing the
> version that was used to create the index can be very useful to know what
> assumptions we can make about an index.
> - Backward compatibility. The codec API helped simplify backward
> compatibility of the index files a lot. However for everything that is done
> on top of the codec API like analysis or the computation of length norm
> factors, backward compatibility needs to be handled on top of Lucene. Maybe
> we could simplify this?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
