You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Adrien Grand (Jira)" <ji...@apache.org> on 2019/11/19 17:00:00 UTC
[jira] [Commented] (LUCENE-9040) Questionable/Underspecified
behavior of DirectoryReader.getIndexCommit() on NRT Readers
[ https://issues.apache.org/jira/browse/LUCENE-9040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16977630#comment-16977630 ]
Adrien Grand commented on LUCENE-9040:
--------------------------------------
I agree there is something to be fixed. I'm not very familiar with index commits, but some things look inconsistent e.g. IndexCommit has a comment that the name is bad as this can also represent a point-in-time view but then the equals/hashcode methods only consider data that identify a commit and that wouldn't change through a reopen, which is why assertions are not failing in your test I guess.
> Questionable/Underspecified behavior of DirectoryReader.getIndexCommit() on NRT Readers
> ---------------------------------------------------------------------------------------
>
> Key: LUCENE-9040
> URL: https://issues.apache.org/jira/browse/LUCENE-9040
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Reporter: Chris M. Hostetter
> Priority: Major
> Attachments: LUCENE-9040.patch
>
>
> It seems like DirectoryReader.getIndexCommit() returns weird
> results when using a "reopened" reader off of uncommited IW changes.
> Even though 2 diff readers will expose diff views of the index, they will
> claim to refer to the same IndexCommit (generation).
> Original email thread (no replies): http://mail-archives.apache.org/mod_mbox/lucene-dev/201910.mbox/%3Calpine.DEB.2.21.1910301611190.8171%40slate%3E
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org