Re: Collector is collecting more than the specified hits

2014-02-18 Thread Michael McCandless
As long as you guarantee your follow-on search uses the same searcher than that's a non-issue. Ie, only a new search could see an index change like a new deletion. Mike McCandless http://blog.mikemccandless.com On Tue, Feb 18, 2014 at 2:32 PM, saisantoshi wrote: > There might be an issue with

Re: Collector is collecting more than the specified hits

2014-02-18 Thread saisantoshi
There might be an issue with the below approach as the docID that is saved might be deleted before the next call to search and I am not sure if it does break the seach functionality when such a thing happens. Thanks, Ranjith. -- View this message in context: http://lucene.472066.n3.nabble.com/

JOB @ Sematext: Professional Services Lead => Head

2014-02-18 Thread Otis Gospodnetic
Hello, We have what I think is a great opening at Sematext. Ideal candidate would be in New York, but that's not an absolute must. More info below + on http://sematext.com/about/jobs.html in job-ad-speak, but I'd be happy to describe what we are looking for, what we do, and what types of companie

Re: Collector is collecting more than the specified hits

2014-02-18 Thread Michael McCandless
You look at the hits you got back, and save the docID of the very last hit, and use that on the follow-on search to get the "next page". This is how searchAfter works ... but you need to ensure you use the same searcher for follow-on requests; otherwise the docIDs are not comparable. E.g. use Sear

RE: Reverse Matching

2014-02-18 Thread Siraj Haider
Thanks Alan. Do you know when we could expect it to be released? regards -Siraj (212) 306-0154 -Original Message- From: Alan Woodward [mailto:a...@flax.co.uk] Sent: Monday, February 17, 2014 4:50 PM To: java-user@lucene.apache.org Cc: 'Ahmet Arslan' Subject: Re: Reverse Matching Hi Sira

Re: Collector is collecting more than the specified hits

2014-02-18 Thread saisantoshi
The above works fine but how do I get the state of *last docID*. Also, there will be multiple users accessing this and we need to maintain the integrity of last docID. Can we know the last docID from the collector collect call? Thanks, Ranjith. -- View this message in context: http://lucene.4

Re: Collector is collecting more than the specified hits

2014-02-18 Thread Michael McCandless
Sorry, searchAfter only works if you are sorting by score or by fields. It seems like you are sorting by docID? Ie, at first you want the top 100 hits sorted by docID, then the next 100, etc.? If so, you could just modify your collector so that you tell it up front the "afterDocID" (= last docID