Jon
I ended up adapting your approach. The solution involves keeping a LRU
cache of page boundary scoredocs and their respective positions. New
positions are added to the cache as new pages are discovered. To cut
down on searches, when scrolling backwards and forwards, the search
begins from
: I was wondering why there is no search method in lucene Indexsearcher to
: search after last reference by passing collector. Say a method with
: signature like searchAfter(Query query, ScoreDoc after, Collector results).
searchAfter only makes sense if there is a Sort involved -- either
explic
Thanks Tim.
I have thought about this for the author field (and like you suggest) it would
probably work. I was actually going to experiment with this later today.
But, I have another field that has a bit more nesting (and it contains authors)
For example, within a given document, I have the f
Hi Darin,
Have you thought about using multivalued fields? If you set the
positionIncrementGap to something kind of big (well > 1, say :) ), and you know
that your data is always authorfirst, authorlast, you could just search for
"darin fulford".
The positionincrementgap will prevent matchin
In a Lucene 3 project originally I only had standard lucene query
syntax, then I needed to additional provide a version of Dismax search
as provided by Solr which I hacked together with some help from someone
on the mailing list (cannot remember who). I've now moved to Lucene 4
and noticed that
Hi,
I was wondering why there is no search method in lucene Indexsearcher to
search after last reference by passing collector. Say a method with
signature like searchAfter(Query query, ScoreDoc after, Collector results).
For normal search there are two ways to search; one by passing the
collector
