You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Simon Willnauer (JIRA)" <ji...@apache.org> on 2010/12/07 16:53:12 UTC
[jira] Assigned: (LUCENE-2805) SegmentInfos shouldn't blindly
increment version on commit
[ https://issues.apache.org/jira/browse/LUCENE-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Willnauer reassigned LUCENE-2805:
---------------------------------------
Assignee: Simon Willnauer
> SegmentInfos shouldn't blindly increment version on commit
> ----------------------------------------------------------
>
> Key: LUCENE-2805
> URL: https://issues.apache.org/jira/browse/LUCENE-2805
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Reporter: Michael McCandless
> Assignee: Simon Willnauer
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2805.patch, LUCENE-2805.patch, LUCENE-2805.patch
>
>
> SegmentInfos currently increments version on the assumption that there are always changes.
> But, both DirReader and IW are more careful about tracking whether there are changes. DirReader has hasChanges and IW has changeCount. I think these classes should notify the SIS when there are in fact changes; this will fix the case Simon hit on fixing LUCENE-2082 when the NRT reader thought there were changes, but in fact there weren't because IW simply committed the exact SIS it already had.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org