e.apache.org
> Subject: AW: Paging with Lucene
>
> The problem is, that due to the "filtering" AFTER having searched the
index,
> we don't know how many TopDocs to read in order have "enough" for page
> x.
>
> Does lucene's search allow injecting kind
> The problem is, that due to the "filtering" AFTER having searched the index,
> we don't know how many TopDocs to read in order have "enough" for page x.
Think of a number and double it? Unless the number get really high
lucene is generally plenty fast enough. Or read n and if, after
filtering
sprüngliche Nachricht-
> Von: Ian Lea [mailto:ian@gmail.com]
> Gesendet: Freitag, 21. Januar 2011 11:10
> An: java-user@lucene.apache.org
> Betreff: Re: Paging with Lucene
>
> The standard recommendation for paging is to re-execute the search for
> second and subsequent pages an
The standard recommendation for paging is to re-execute the search
for second and subsequent pages and return the second or subsequent
chunk of hits. Would that not work in your case?
An alternative is to read and cache hits from the initial search but
that is generally more complex.
--
Ian.
O
(thanks fort he many answers to my initial lucene question "Best practices for
multiple languages?")
We shall be confronted with the followong problem:
due to the very dynamic access rules on our content, we shall not be able to
formulate these in/as Filter(s).
Hence we need to first search and
