[
https://issues.apache.org/jira/browse/LUCENE-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562134#comment-14562134
]
Robert Muir commented on LUCENE-6505:
-------------------------------------
+1
{quote}
I explored removing SegmentInfos.lastGeneration
{quote}
Its too bad that didnt work out... for now it lives...
> NRT readers don't always reflect last commit
> --------------------------------------------
>
> Key: LUCENE-6505
> URL: https://issues.apache.org/jira/browse/LUCENE-6505
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: Trunk, 5.3
>
> Attachments: LUCENE-6505.patch
>
>
> Two cases here:
> * When I pull an NRT reader from IW,
> IR.getIndexCommit().getSegmentsFileName() should reflect what was
> last committed, but doesn't now
> * If I call IW.commit(), or IW.setCommitData(), but make no other
> changes, and then open a new NRT reader, I think it should reflect
> the new commit, but doesn't now
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
