lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-1726) Deep Paging and Large Results Improvements
Date Wed, 01 Feb 2012 16:46:59 GMT


Yonik Seeley commented on SOLR-1726:

You seemed to agree that it should be the external ID previously.

bq. Why is it any more dangerous than the action itself? If the reader has changed, this whole
act is unnatural to begin with.

It's the degree of breakage.  Small change to index should yield a small amount of potential
breakage - and it can be catastrophic (in unpredictable ways) if using internal docids.
> Deep Paging and Large Results Improvements
> ------------------------------------------
>                 Key: SOLR-1726
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            Priority: Minor
>             Fix For: 4.0
>         Attachments:,,,,
SOLR-1726.patch, SOLR-1726.patch,,,
> There are possibly ways to improve collections of "deep paging" by passing Solr/Lucene
more information about the last page of results seen, thereby saving priority queue operations.
  See LUCENE-2215.
> There may also be better options for retrieving large numbers of rows at a time that
are worth exploring.  LUCENE-2127.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message