Also, in 3.5.0 there is a new API in IndexSearcher: searchAfter.
It enables you to efficiently collect hits only after the previous
last page's last hit.
It should be faster, in proportion to how deeply you page... but most
apps do not need to do deep paging so simply collecting all hits up
throu
The latter: do the search again and grab the chunk you want. Best not
to open the index each time if you can avoid it.
http://wiki.apache.org/lucene-java/LuceneFAQ#How_do_I_implement_paging.2C_i.e._showing_result_from_1-10.2C_11-20_etc.3F
--
Ian.
On Tue, Nov 15, 2011 at 12:05 PM, Felipe Carval
I've found a couple of people asking around the same thing over the
internet, just wanted to check with the experts if there's a better way to
do this: how do I paginate Lucene search results? Is there a native way to
do this or should I, upon each request, open the index, do the search and
get the
While you are correct that as a general rule it can't be done, there
is nothing stopping you from trying in your particular circumstances,
with an unchanging index and standard queries. Look at the scores and
the matches and decide where the good/bad threshold lies and hard code
that in your appli
hey folks,
we lately looked into
https://issues.apache.org/jira/browse/LUCENE-3235 again, an issue
where a class using ConcurrentHashMap hangs / deadlocks on specific
JVMs in combination with specific CPUs. It turns out its a JVM bug in
Sun / Oracle Java 1.5 as well as Java 1.6. Its apparently fix
Hi Nishesh,
The index corruption may be caused by one of the bugs in the used JDK
version. From your checkindex output, you are using 1.6.0_02, which is
really old. This Lucene Wiki page lists a lot of bugs in those old JVMs:
http://wiki.apache.org/lucene-java/SunJavaBugs
Many of them may also ca
