lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Updated: (LUCENE-2829) improve termquery "pk lookup" performance
Date Tue, 21 Dec 2010 20:39:01 GMT


Robert Muir updated LUCENE-2829:

    Attachment: LUCENE-2829.patch

quickly hacked up patch, 

for the IndexSearcher case, we sum up docFreq ourselves, along the way saving the hashcodes
of the readers where the term exists into a set.

if this list exists (IndexSearcher case), the scorer then checks the reader's hashcode against
this list...
if we get a collision, worst case we do a wasted seek. but we don't have to keep any hairy
to readers or anything.

> improve termquery "pk lookup" performance
> -----------------------------------------
>                 Key: LUCENE-2829
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Robert Muir
>         Attachments: LUCENE-2829.patch
> For things that are like primary keys and don't exist in some segments (worst case is
primary/unique key that only exists in 1)
> we do wasted seeks.
> While LUCENE-2694 tries to solve some of this issue with TermState, I'm concerned we
could every backport that to 3.1 for example.
> This is a simpler solution here just to solve this one problem in termquery... we could
just revert it in trunk when we resolve LUCENE-2694,
> but I don't think we should leave things as they are in 3.x

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:
For additional commands, e-mail:

View raw message