[
https://issues.apache.org/jira/browse/LUCENE-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421185#comment-13421185
]
roman commented on LUCENE-4242:
-------------------------------
My use case was to get an un-inverted index of a multiValued field - I use it
to make 2nd-pass queries (e.g. find all docs that are referencing docs found in
the 1st pass). I had my own code to create the univerted index (in the 3.x
release) but wanted st standard - so this is how I noticed the difference
between the branches.
However, if I let DocTermOrds manage the un-inverted cache, I can fully switch
(I hope).
But as this un-inverted index is used for faceting, isn't it possible there
will be errors in the faceting? Some terms missing?
> UnInverted cache uses term freq to filter out terms (but deleted docs are
> included in the freq count)
> -----------------------------------------------------------------------------------------------------
>
> Key: LUCENE-4242
> URL: https://issues.apache.org/jira/browse/LUCENE-4242
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/index
> Affects Versions: 4.0
> Reporter: roman
> Priority: Minor
> Attachments: LUCENE-4242.patch, LUCENE-4242.patch, LUCENE-4242.patch
>
>
> TermEnum.docFreq() count is used to compute uninverted index
> (DocTermOrds.uninvert()). The code goes like:
> final int df = te.docFreq();
> if (df <= maxTermDocFreq) {
> So, if there are deleted documents in the index and maxTermDocFreq is
> low, then the term will be excluded (even if the freq of the livedocs
> is OK). Most likely, the cache will be incomplete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
