[
https://issues.apache.org/jira/browse/LUCENE-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703333#action_12703333
]
Matt Chaput edited comment on LUCENE-1613 at 4/27/09 1:11 PM:
--------------------------------------------------------------
Given how fundamental the issue is w.r.t. how Lucene stores the index, it's
unlikely to ever be fixed. (A clean, performant fix other than simply merging
the segments would be a pretty incredible revelation.) As an outside observer I
would argue against keeping the bug open forever for correctness sake.
was (Author: mchaput):
Given how fundamental the issue is w.r.t. how Lucene stores the index, it's
unlikely to ever be fixed. (A clean, performant fix other than simply merging
the segments would be pretty incredible revelation.) As an outside observer I
would argue against keeping the bug open forever for correctness sake.
> TermEnum.docFreq() is not updated with there are deletes
> --------------------------------------------------------
>
> Key: LUCENE-1613
> URL: https://issues.apache.org/jira/browse/LUCENE-1613
> Project: Lucene - Java
> Issue Type: Bug
> Components: Search
> Affects Versions: 2.4
> Reporter: John Wang
> Attachments: TestDeleteAndDocFreq.java
>
>
> TermEnum.docFreq is used in many places, especially scoring. However, if
> there are deletes in the index and it is not yet merged, this value is not
> updated.
> Attached is a test case.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
