[
https://issues.apache.org/jira/browse/LUCENE-9324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17086438#comment-17086438
]
ASF subversion and git services commented on LUCENE-9324:
---------------------------------------------------------
Commit 113043b1ed2ac95de17f6bdd203f6050ff6ca1f7 in lucene-solr's branch
refs/heads/master from Simon Willnauer
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=113043b ]
LUCENE-9324: Add an ID to SegmentCommitInfo (#1434)
We already have IDs in SegmentInfo, as well as on SegmentInfos which are useful
to uniquely identify segments and entire commits. Having IDs on
SegmentCommitInfo is be useful too in
order to compare commits for equality and make snapshots incremental on
generational files.
This change adds a unique ID to SegmentCommitInfo starting from Lucene 8.6.
Older segments won't have an ID until the segment receives an update or a
delete even if they have been opened and / or committed by Lucene 8.6 or above.
> Give IDs to SegmentCommitInfo
> -----------------------------
>
> Key: LUCENE-9324
> URL: https://issues.apache.org/jira/browse/LUCENE-9324
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Adrien Grand
> Assignee: Simon Willnauer
> Priority: Minor
> Fix For: master (9.0), 8.6
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> We already have IDs in SegmentInfo, which are useful to uniquely identify
> segments. Having IDs on SegmentCommitInfo would be useful too in order to
> compare commits for equality and make snapshots incremental on generational
> files too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
