lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (LUCENE-2215) paging collector
Date Fri, 26 Mar 2010 10:40:27 GMT


Grant Ingersoll commented on LUCENE-2215:

bq. Let's be careful about the semantics here Grant. Most if not all applications implement
paging indeed, but I believe only FEW actually store user contexts between searches. PagingCollector
relies on the application to store the lowest ranking doc that was returned previously, which
means storing context between user's searches.

I think, assuming the math plays out, that once you show the gains to be had here, esp. for
deep paging, storing an int and a float is trivial.  If they are implementing paging, they
are already keeping state about what page they are on.  

bq. Now they will need to think "where do I get this low score from?"

Sorry, but If that is that hard to figure out, then I don't see how they have any business
writing a Lucene application to begin with.  A simple javadoc that says these two values are
taken from the last result of the previously seen page should do the trick

At any rate, let's put up the patches and find out instead of debating.  I should have time
today to do mine.

> paging collector
> ----------------
>                 Key: LUCENE-2215
>                 URL:
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: Search
>    Affects Versions: 2.4, 3.0
>            Reporter: Adam Heinz
>            Assignee: Grant Ingersoll
>            Priority: Minor
>         Attachments:, LUCENE-2215.patch,,
> Somebody assign this to Aaron McCurry and we'll see if we can get enough votes on this
issue to convince him to upload his patch.  :)

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